cherry_pick
Claims items for work. This is STEP 1 — ALWAYS pick before doing any work. NEVER do work without calling this first. Requires idempotency_key. Pass item_numbers from the display (e.g. [3] for item 3), or set pick_all=true to pick all todo items. Show the display field to the user verbatim in a code block.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"idempotency_key": "<idempotency_key>"
},
"name": "cherry_pick"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| item_ids | No | Alternative to item_numbers — UUIDs from structuredContent. Most agents should use item_numbers instead. | |
| pick_all | No | If true, pick all todo items in the current project. When set, item_numbers and item_ids are ignored. | |
| item_texts | No | Display only — the text of each item being cherry-picked, for human-readable permission prompts. Ignored by the server. | |
| item_numbers | No | The item NUMBERS to cherry-pick, as shown in the display from get_items. This is what the user means when they say "work on item 3". Preferred over item_ids. | |
| idempotency_key | Yes | A unique string for this cherry-pick request. Reusing the same key with the same items returns the same result (idempotent). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| picked | Yes | ||
| display | Yes | Pre-formatted confirmation. Show this to the user verbatim in a code block. |