Skip to main content
Glama

Block a task with a question

taskhold_block

Mark 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

NameRequiredDescriptionDefault
reasonYesOne answerable question, e.g. "Approve: deploy the migration to staging now?"
optionsNo2-4 short choices shown as buttons, e.g. ["Postgres", "SQLite", "Ask me later"]. Omit for an open question.
task_idYesThe ID of the task to block
recommendedNoIndex into options of the one you recommend (0 = the first). Marked on the board.
if_no_answerNoWhat you will do if nobody answers, e.g. "I'll use SQLite and keep going in 30 min."

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / task_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare the non-destructive, local write profile, but the description adds substantial behavior the agent could not infer: the return payload (the question plus the exact taskhold_updates call to wait with), where it appears on the board (Needs you), and how re-blocking an already-blocked task merges the new question while preserving history. It even documents the failure mode for an unknown task_id ("Task not found").

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose and trigger, then flows into mechanics and edge cases; nearly every sentence earns its place. Slight redundancy in restating the wait call twice ("Returns the exact taskhold_updates call" and "Wait for the reply with taskhold_updates {task_id, since, wait: 50}").

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no output schema, the description covers everything an agent needs: return shape, board visibility, the required follow-up call with literal arguments, re-block semantics, and error behavior. Nothing material is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: how to phrase reason as one answerable question, when to supply options versus omit them, the role of recommended and if_no_answer, and how the reply string will read back. Minor gap: no guidance on keeping if_no_answer consistent with the recommended option.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — "Mark a task (or step) blocked" — plus the condition that triggers it. It is clearly distinguishable from siblings like taskhold_unblock and taskhold_updates, which it names directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use with concrete triggers (a decision, missing info, access), plus a named alternative for the follow-up action (taskhold_updates with wait). It also says what NOT to do — "don't guess" — and what to do instead if the reply doesn't settle the question.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources