Skip to main content
Glama

add_comment

Adds a comment to a specified Kaiten task card, letting AI assistants post updates and notes directly to tasks during kanban workflows.

Instructions

Add a comment to a task. Max useful body is truncated for context.

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": {
      "card_id": "<card_id>",
      "text": "<text>"
    },
    "name": "add_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
card_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
textYes
card_idYes
createdYes
_metricsNo
author_idYes
truncatedNo
text_charsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare this as a non-readonly, non-idempotent, open-world, non-destructive write. The description adds one behavioral claim — 'Max useful body is truncated for context' — but it is ambiguous: it never says whether the stored comment is truncated, whether the returned context is truncated, or what the limit is. It also omits permission requirements and whether repeating the call creates duplicates, which matters given idempotentHint=false.

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?

Two short sentences with no padding, which is appropriately sized. However, the second sentence is vague enough that it reads as filler rather than useful front-loaded information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, but for a two-parameter write tool with zero schema descriptions the definition is under-specified. The identifier parameter and the truncation behavior both need at least one clarifying clause.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters, so the description must carry the burden and does not. It loosely implies a text body, but card_id is never mentioned and the card-versus-task identifier question is left open, so an agent gets no meaning beyond bare property names.

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?

"Add a comment to a task" gives a specific verb plus resource and is distinguishable from the sibling list_comments (which reads rather than writes). It stops short of a 5 because the resource is called a 'task' while the required parameter is card_id, leaving a naming ambiguity the agent must resolve itself.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus list_comments or the tag-mutation siblings, and no stated preconditions. The only usage hint is a truncated note about body size, which is not a selection rule.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.