Skip to main content
Glama

KanbanMCP

Finish a card with a handoff

complete

Ends your run with a handoff. The card moves to Done. It goes to Review when a question on it still waits for a person. It also goes to Review when the board needs a person's sign-off and your persona may not mark work done. Your claim ends. In a batch it ends 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>",
      "summary": "<summary>",
      "metadata": "<metadata>"
    },
    "name": "complete"
  }
}

Input Schema

NameRequiredDescriptionDefault
doneNoMark it Done. Only has an effect where a person signs off.
prUrlNoPull request URL (https), saved on the card you hold.
runIdNoRun id from claim_next.
cardIdYesCard id, number (12) or key (WEB-12).
boardIdNoBoard id or slug.
changesNoOn a claim from Review: send the card back to Ready. summary gives the steps.
personaNoThe persona to act as.
summaryYesWhat you did and why, including options you ruled out.
metadataYesThe handoff: files_changed, verification (what you ran and saw), residual_risk (text, or "none"). Add commit_sha and test_output when the claim has handoffNeeds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the tool is a non-read-only, non-idempotent state transition. The description adds meaningful behavioral detail beyond them: the card moves to Done or Review depending on open questions or sign-off requirements, the caller's claim ends, and batch calls affect only the current card.

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?

The description is short, front-loaded with the primary effect ('Ends your run with a handoff'), and each sentence contributes a distinct routing rule or scope clarification. There is no filler.

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 complex 9-parameter mutation with nested metadata and no output schema, the description covers the central state transitions, claim ending, and batch behavior. It leaves finer details such as idempotency or error handling to the schema and annotations, which is acceptable but not exhaustive.

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 parameter semantics are already documented in the input schema. The description does not add syntax or format details for cardId, runId, done, changes, or metadata beyond what the schema provides, making the baseline 3 appropriate.

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?

The description states a specific verb ('Ends your run') and resource ('card') and explains the handoff outcome. It clearly differentiates this completion step from column or card mutation tools, though it does not explicitly name sibling tools like release or stop_run.

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?

It gives clear conditions for when the card goes to Done versus Review, including question-waiting and sign-off cases, and notes batch scope. However, it does not compare against alternatives such as release or stop_run, leaving the choice partly implied.

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