Block a task with a question
taskhold_blockMark a task (or step) blocked when you can't continue without the person (a decision, missing info, access). Returns the question and the exact taskhold_updates call to wait with. Write the reason as one question they can answer from the board in a line, e.g. "Decide: drop the legacy column or keep it nullable?". When the answer is a choice, pass 2-4 short options (with recommended and if_no_answer): the person answers with one tap and the reply reads Reply to "": chose "". The board shows it under Needs you. Wait for the reply with taskhold_updates {task_id, since, wait: 50}; keep working on anything that doesn't depend on it meanwhile. If the reply doesn't settle it, block again with a narrower question; don't guess. Blocking an already-blocked task asks the new question instead, and the earlier question stays in the task's history; an unknown task_id fails with "Task not found".
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": {
"task_id": "<task_id>",
"reason": "<reason>"
},
"name": "taskhold_block"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| reason | Yes | One answerable question, e.g. "Approve: deploy the migration to staging now?" | |
| options | No | 2-4 short choices shown as buttons, e.g. ["Postgres", "SQLite", "Ask me later"]. Omit for an open question. | |
| task_id | Yes | The ID of the task to block | |
| recommended | No | Index into options of the one you recommend (0 = the first). Marked on the board. | |
| if_no_answer | No | What you will do if nobody answers, e.g. "I'll use SQLite and keep going in 30 min." |