Build Tools
The tracker of a project: its stories, tasks, sub-tasks, bugs, spikes and improvements, each numbered from the same sequence as the epics (`CRM-142`) with its kind, status from the backlog to done, resolution, priority, the people on it, its estimates and dates, the fields its kind adds and, for a story, the acceptance criteria that say when it is done.
The tracker of a project: its stories, tasks, sub-tasks, bugs, spikes and improvements, each numbered from the same sequence as the epics (CRM-142) with its kind, status from the backlog to done, resolution, priority, the people on it, its estimates and dates, the fields its kind adds and, for a story, the acceptance criteria that say when it is done. These tools read a project's backlog and what is assigned to the person the token acts as (a guest token the agreed items only), read one item with its criteria before it is implemented or tested, move an item along its lifecycle with a resolution on a close, and hand it to a member of the team; create an item of any kind with everything set at once (create_work_item), change one in part with its criteria, components and labels (update_work_item) and delete one after a confirmation; the move and the hand-over are destructive in the MCP sense, so an agent confirms before moving or taking work that is not the person's. The labels are the project's own words pinned on its items, each with a colour and a meaning; an agent reads them (list_labels), filters the backlog by one, and coins, renames and removes them (create_label, update_label, delete_label) under the same permission that changes an item. The sprints the team plans and commits to are read here too (list_sprints: the running sprint, the planned ones and the closed ones with their velocity; get_sprint: one sprint with the items it holds and its points), and an item is planned into a sprint through its own sprint_id on update_work_item; planning, starting, closing and cancelling a sprint stay in the application and the REST API. The board is read here too (get_board_snapshot: the columns the project keeps in order with their limits, tallies and cards, for the running sprint, a sprint by id, every open item or the unplanned ones), and a card's column changes through move_work_item under the same lifecycle and limits; ranking a card stays in the application and the REST API. Time logs and code links join as each module lands.
Tools
assign_work_itemAssign Work ItemDESTRUCTIVEcreate_labelCreate LabelDESTRUCTIVEcreate_work_itemCreate Work ItemDESTRUCTIVEdelete_labelDelete LabelDESTRUCTIVEdelete_work_itemDelete Work ItemREADget_board_snapshotGet Board SnapshotREADget_sprintGet SprintREADget_work_itemGet Work ItemREADlist_labelsList LabelsREADlist_my_workList My WorkREADlist_sprintsList SprintsREADlist_work_itemsList Work ItemsDESTRUCTIVEmove_work_itemMove Work ItemDESTRUCTIVEupdate_labelUpdate LabelDESTRUCTIVEupdate_work_itemUpdate Work ItemHow is this guide?
Last updated on