Skip to main content
Glama

KanbanMCP

Block a card

block

Ends your run because you cannot continue, with a typed reason. The card leaves Running and your claim ends. Use it only for something outside your control. A card that does not suit you is for release. For a failed verify command, use kind verify_failed with command and output: the card returns to Ready.

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": {
      "cardId": "<cardId>",
      "kind": "<kind>"
    },
    "name": "block"
  }
}

Input Schema

NameRequiredDescriptionDefault
onNoFor waiting: the card to wait for.
kindYesWhy you cannot continue.
runIdNoRun id from claim_next.
untilNoA time (ISO) when the card comes back to you.
cardIdYesCard id, number (12) or key (WEB-12).
outputNoFor verify_failed: what it printed. Strip secrets first.
reasonNoSay it for the next reader. Include no secrets. Needed unless verify_failed.
boardIdNoBoard id or slug.
commandNoFor verify_failed: the command that ran.
optionsNoFor needs_input: 2 to 6 answers, as in raise. Mark your advice. None means Approve or Decline.
personaNoThe persona to act as.
questionNoThe question. Needed with needs_input.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare the mutation profile (readOnlyHint false, destructiveHint false, idempotentHint false), so the safety burden is partly lifted; the description then adds real state semantics — the card leaves Running, your claim ends, and in the verify_failed case the card returns to Ready. It also warns about secrets in reason/output. It does not explain whether a blocked card can be re-blocked or what the caller should do after blocking, so it stops short of a 5.

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

Conciseness5/5

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

Four short sentences, front-loaded with the effect before the constraints, then the special-case branch. Every sentence carries decision-relevant information; nothing is padding.

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

Completeness4/5

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

For a 12-parameter mutation tool with no output schema, the description covers the primary decision path and the most error-prone branch (verify_failed) and defers the remaining kind-specific fields to the schema, which is fully documented. The waiting/needs_input paths are handled only by schema descriptions, leaving a small gap in the description's coverage.

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 the baseline is 3, but the description goes beyond field definitions by tying specific enum values to their companion fields ('kind verify_failed with command and output') and by implying which kinds map to which field sets. It does not cover the waiting kind's on/until pairing or needs_input's question/options, so not a 5.

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 (ends your run) and the state transition it causes (the card leaves Running, your claim ends), which is exactly what distinguishes it from the many other card-state tools in the sibling list. It also names the sibling it is NOT: 'A card that does not suit you is for release.'

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 ('only for something outside your control'), explicit exclusion routing to 'release', and a concrete conditional branch ('For a failed verify command, use kind verify_failed with command and output'). That is the full when/when-not/alternative triad.

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