Skip to main content
Glama

KanbanMCP

Move a card

move_card
DestructiveIdempotent

Moves a card to a state or to an exact column. Pass summary with a move to Ready to send the card back for changes. Pass clearWait to let agents claim the card again now.

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

Input Schema

NameRequiredDescriptionDefault
stateNolater, triage, todo, ready, running, blocked, review or done.
cardIdYesCard id, number (12) or key (WEB-12).
columnNoA column, by id or label.
boardIdNoBoard id or slug.
confirmNoNeeded to move a card into Done or Blocked.
personaNoThe persona to act as.
summaryNoWith a move to Ready: send the card back for changes, and say what to change.
columnIdNoA column, by id or label.
clearWaitNoLet agents claim the card again now. Clears its saved pull request link and its wait. With no state or column, it moves nothing.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotent=true, so the safety profile is covered. The description adds genuinely new behavioral context: summary on a Ready move sends the card back for changes, and clearWait clears the saved pull request link and wait. It omits the confirm requirement for Done/Blocked, which the schema happens to carry.

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?

Three short sentences, zero filler, and the core action plus its two non-obvious parameter behaviors are front-loaded. Every sentence earns its place.

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 9-parameter mutation tool with no output schema, the description covers the action and the two easily-misused parameters. It leaves the confirm-gated Done/Blocked moves and the boardId/persona context to the schema, which is acceptable given full schema coverage, but a note on the confirm gate would have completed it.

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 every parameter including summary, clearWait and confirm is already documented in the schema; the description largely restates summary/clearWait semantics. Baseline 3 is appropriate since the schema does the heavy lifting and the description adds no syntax or format detail beyond it.

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

Purpose4/5

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

States a specific verb and resource ('Moves a card') and immediately disambiguates the two targeting modes: a state or an exact column. It does not, however, distinguish itself from siblings that also change card status (promote, complete, block, release), so an agent must infer the boundary.

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?

Gives conditional guidance for two parameters ('Pass summary with a move to Ready', 'Pass clearWait to let agents claim the card again now'), which implies usage. But it never says when to use move_card versus promote, complete, block, or release, nor when-not to use it, so the routing guidance is only partial.

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