Skip to main content
Glama

KanbanMCP

Send a card to review

request_review

Ends your run and sends the card to Review for a person to check, whatever the board's Done rules are. Takes the same handoff as complete. It clears the assignee. Pass reviewer to name who reviews.

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

Input Schema

NameRequiredDescriptionDefault
ownerNoA person (name or id) to own a card with no owner.
prUrlNoPull request URL (https), saved on the card you hold.
cardIdYesCard id, number (12) or key (WEB-12).
columnNoA Review column, by id or label.
boardIdNoBoard id or slug.
personaNoThe persona to act as.
summaryYesWhat you did and why, and what to check.
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.
reviewerNoWho should review it.
ownerNoteNoWhy, for that person.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses meaningful side effects: it ends the run, clears the assignee, and overrides the board's Done rules. Those are exactly the non-obvious behavioral traits an agent needs before committing to the call.

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, front-loaded with the primary effect and side effects, with zero 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 10-parameter tool with a nested metadata object, the description pairs well with full schema coverage and explains the key non-schema behavior. What happens on missing handoffNeeds or validation failure is not covered, leaving a small gap.

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; the description adds value by explaining the 'handoff' metadata requirement by analogy to complete and explicitly flagging the reviewer parameter's purpose. It stops short of clarifying owner/ownerNote interactions.

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?

Names a specific action (sends the card to Review, ends your run) and distinguishes itself from the sibling 'complete' by noting it bypasses the board's Done rules. An agent can tell exactly what this does and what it is not.

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?

'Ends your run and sends the card to Review for a person to check' gives a clear triggering context, and 'Takes the same handoff as complete' routes the agent to the related workflow. It doesn't state explicit when-not conditions, keeping it just 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