Skip to main content
Glama

KanbanMCP

Hand a card back

release
DestructiveIdempotent

Ends a reading claim, or hands back a card you hold when it does not suit you, or not now. It goes back where it was and counts for nothing. You do not get it again, unless you pass until. In a batch it hands back that card only.

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": "release"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoA persona that may suit it; it is mentioned in a comment.
runIdNoRun id from claim_next.
untilNoA time (ISO) when the card comes back to you.
cardIdYesCard id, number (12) or key (WEB-12).
effortNoThe effort the card needs, so a stronger agent takes it.
reasonNoWhy it does not suit you. Include no secrets.
boardIdNoBoard id or slug.
personaNoThe persona to act as.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds useful state semantics beyond them — the card 'goes back where it was and counts for nothing' and is not re-offered unless 'until' is set. That is real behavioral value, though the obtuse phrasing dilutes it.

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

Conciseness3/5

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

It is short (three sentences) but not front-loaded: the leading clause mixes 'Ends a reading claim' with 'hands back a card you hold when it does not suit you, or not now,' and the dangling 'or not now' muddies the opening. Compact but structurally loose.

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?

With 8 params but full schema coverage and no output schema, the description only needs to frame the action and its side effects, which it does. Annotations cover the safety profile and the schema covers the inputs, so nothing critical for a correct call is missing.

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 description coverage is 100%, so the schema already documents all 8 parameters, giving a baseline of 3. The description only faintly gestures at 'until' ('unless you pass until'); it adds essentially no meaning beyond the schema's own descriptions for to, reason, effort, runId, or boardId.

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

Purpose3/5

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

The description conveys that 'release' ends a claim or hands a held card back to its origin, which names a verb and outcome. However, jargon like 'reading claim' is undefined and no sibling (complete, block, stop_run, undo) is named to distinguish it. The agent can guess the core action but not cleanly separate it from adjacent lifecycle tools.

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

Usage Guidelines3/5

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

It implies when to use it ('when it does not suit you, or not now') and notes the consequence ('you do not get it again, unless you pass until'). But it names no alternatives and gives no contrast with complete, block, or complete-adjacent tools, so the selection guidance stays implied rather than explicit.

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