Skip to main content
Glama

list_comments

Read-onlyIdempotent

Retrieve comments for a Kaiten task with truncated message bodies to review discussion context quickly.

Instructions

List comments for a task with compact truncated bodies.

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>"
    },
    "name": "list_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
card_idYes

Output Schema

NameRequiredDescriptionDefault
countYes
itemsYes
card_idNo
_metricsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral trait beyond that: comment bodies are returned compact and truncated. It does not disclose truncation limits, ordering, or pagination behavior, so the added context is real but thin.

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?

One short sentence with the key qualifier ('compact truncated bodies') front-loaded and no filler. It is efficient, though the extreme terseness leaves no room for the operational details an agent would benefit from.

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

Completeness3/5

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

Because an output schema exists, return structure need not be described, and the tool is a simple one-parameter list. Still, for a tool whose defining characteristic is truncated bodies, the definition should say how truncation affects usability (e.g., whether full bodies require another call) and whether results are ordered or paginated.

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 0%, so the description must carry the parameter's meaning. 'For a task' does explain that the single id selects a task's comments, though the schema calls the field card_id while the description calls it a task — a small terminology gap that leaves the mapping slightly ambiguous.

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 and resource: 'List comments for a task.' An agent can distinguish it from the write-side sibling add_comment and from list_tasks/list_boards without opening the schema. It does not, however, name a sibling or scope the listing (per-task is implied by the required id).

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 explicit when-to-use guidance, no prerequisite or permission note, and no mention of alternatives such as add_comment when the intent is to write rather than read. Usage must be inferred from the verb 'list' alone.

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