Skip to main content
Glama

get_task_comments

Read-onlyIdempotent

Retrieve comments for a specific task in newest-first order, including author names and mentions, with an option to include deleted comments.

Instructions

Comments on a task, newest first, with author names and mentions.

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": {
      "task_id": "<task_id>"
    },
    "name": "get_task_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes
include_deletedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description contributes the noteworthy behavior that results are ordered newest-first and include author names and mentions, but it omits pagination/result-size behavior and says nothing about what include_deleted actually does.

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?

A single front-loaded sentence with no filler; the ordering and content hints come before anything else. It is efficient, though slightly clipped (no verb like "list") and the brevity is part of why key parameters go unexplained.

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?

An output schema exists, so return values need not be spelled out, and annotations cover the safety profile. For a comments listing that could be lengthy, though, the absence of any pagination or limit guidance and the unexplained include_deleted flag leave real gaps.

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%, so the description must carry both parameters, yet it explains neither task_id nor include_deleted. The include_deleted flag is the more consequential one — whether deleted comments appear and in what form — and it is left entirely undocumented beyond its default in the schema.

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?

"Comments on a task" names a specific resource and scope, and adds useful shape (newest-first ordering, author names, mentions) that tells an agent what comes back. It does not explicitly distinguish itself from the write-side siblings (add_task_comment, edit_task_comment, delete_task_comment), so the read/write split is inferred rather than stated.

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 when-to-use guidance at all: no mention of when to call this versus get_task/get_task_history, no prerequisites, and no note about needing read access to the parent task. The agent must infer everything from the name and one sentence of prose.

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