Skip to main content
Glama

KanbanMCP

Comment on a card

comment

Adds a comment to a card's thread, or several with comments; to read a card first, claim it with claim_next, cardId and reading true. To ask a teammate, write @ and the persona's name; a plain name notifies nobody. At three agent comments in a row, stop and leave it to a person. Write short. Use 20 words or fewer in a sentence. Put the result first, then the reason, then what you need.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoThe comment. @name notifies a person or persona.
runIdNoRun id from claim_next.
cardIdNoCard id, number (12) or key (WEB-12).
boardIdNoBoard id or slug.
personaNoThe persona to act as.
verdictNoYour review result. Send it on the comment that ends a review of a card in Review. Everyone who looks at the card sees it.
commentsNoSeveral comments: each has cardId and body. An item may take verdict.
idempotencyKeyNoThe same key again adds one comment. Items in comments take it too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover write/idempotency/destructive flags, so the lower bar applies, and the description genuinely adds behavior beyond them: notification semantics for @mentions, the three-comment escalation rule, and brevity expectations. It does not explain idempotencyKey behavior, which the schema alone carries. No contradiction with readOnlyHint=false / destructiveHint=false.

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?

The functional information is front-loaded and each imperative carries a rule. A few sentences drift into editorial style policing (word counts) that is useful but less essential than the omitted idempotency guidance.

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 an eight-parameter, zero-required write tool with no output schema, the description covers the operative workflow (claim, comment, mention, verdict, escalation). Only peripheral parameters like boardId, persona, and idempotencyKey rely solely on the schema, which is acceptable given 100% coverage.

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 eight parameters, warranting the baseline 3. The description adds relational context for cardId/runId (claim_next flow) and comments, but no syntax or format detail beyond what the schema states.

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 opening sentence names a specific verb and resource ('Adds a comment to a card's thread') and extends to batch posting via the comments array. It is clearly distinct from siblings like update_card or create_card, though the phrase 'or several with comments' is clipped and slightly awkward.

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 actionable conditions: claim the card with claim_next before reading, use @ for teammates and understand a plain name notifies nobody, and stop after three consecutive agent comments. It lacks an explicit statement of when NOT to comment versus using another tool (e.g. verdict on update_card), but the routing guidance present is concrete.

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