Skip to main content
Glama

KanbanMCP

Stop a running claim

stop_run
DestructiveIdempotent

Ends the active run on a card now. The claim ends and the card goes back to Ready. Use it when an agent is stuck, wrong, or must be cut off. In a batch it stops that card only; batch true stops all.

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>"
    },
    "name": "stop_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
batchNoStop the whole batch. Left out, only this card stops.
cardIdYesCard id, number (12) or key (WEB-12).
boardIdNoBoard id or slug.
personaNoThe persona to act as.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, so safety is covered structurally. The description adds genuine context beyond that: the claim is ended and the card reverts to Ready, and the batch flag widens the blast radius to all cards. It still doesn't say whether the interrupted work is lost or whether any confirmation/permission is needed.

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?

Four short, front-loaded sentences with no filler; the scope statement leads and the batch caveat follows. Slight redundancy between 'Ends the active run' and 'The claim ends', but it is minor and readable.

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 destructive, idempotent mutation with no output schema and fully documented parameters, the description supplies the essential missing context: the card's post-state and the batch scope. It is nearly complete, lacking only an explicit tie-breaker against sibling stop/release tools.

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

Parameters3/5

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

Schema coverage is 100%, so every parameter is already documented in the input schema. The description reinforces batch semantics ('batch true stops all') but adds no new syntax or format detail beyond the schema's own 'Stop the whole batch' text, making the baseline 3 appropriate.

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+resource ('Ends the active run on a card') and immediately describes the resulting state change (claim ends, card returns to Ready). That outcome distinguishes it from siblings like release, complete, block, or undo without naming them.

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

Usage Guidelines4/5

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

Gives explicit when-to-use conditions ('agent is stuck, wrong, or must be cut off') and scopes the batch case ('stops that card only; batch true stops all'). It does not name the closest alternative tools (release/complete) or state when NOT to use it, so it stops short of a 5.

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