Skip to main content
Glama
bim-ba

ycli

by bim-ba
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Tracker issue comment

tracker_comments_get
Read-onlyIdempotent

Fetch one Tracker issue comment by issue key and comment ID to read its text, author, edit history, and optionally attachments or HTML.

Instructions

One comment of a Tracker issue: text, author, edit history and, on request, attachments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
expandNoExtra fields: ``attachments``, ``html`` or ``all`` (comma-separated).
issue_keyYesIssue key, e.g. QUEUE-123.
comment_idYesComment id (numeric ``id`` or ``longId``), from ``comments_list``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.122.1
    • addedInput schema / properties / comment_id / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "string"
+  }
+]
    • removedInput schema / properties / comment_id / type
      Removed value: -"string"
    • addedInput schema / properties / issue_key
      Added value: +{
+  "description": "Issue key, e.g. QUEUE-123.",
+  "type": "string"
+}
    • removedInput schema / properties / key
      Removed value: -{
-  "description": "Issue key, e.g. QUEUE-123.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "key",
-  "comment_id"
-]New value: +[
+  "issue_key",
+  "comment_id"
+]
  2. First observedv0.67.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, idempotentHint and openWorldHint, so the safety profile is covered. The description adds useful return-content information (text, author, edit history, attachments only 'on request'), which partially compensates for the absent output schema.

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 resource and its fields come first. Efficient, though the fields list is slightly telegraphic.

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?

Low-complexity read tool with no output schema; the description does describe what is returned, covering the main gap. Only finer return-format details (e.g., edit-history shape) are left unspecified, which is acceptable for such a simple fetch.

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 all three parameters (issue_key, comment_id, expand) are documented in the schema itself. The phrase 'on request, attachments' loosely hints at the expand parameter but adds no syntax or format detail beyond it. Baseline 3 applies.

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?

States a specific verb (Get) and resource (one comment of a Tracker issue) and enumerates the payload fields (text, author, edit history, attachments). The singular 'one comment' implicitly distinguishes it from tracker_comments_list, though no sibling is named explicitly.

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?

No explicit when-to-use statement and no alternatives named. The agent can infer it retrieves a single comment by id, but the description offers no routing guidance versus tracker_comments_list or tracker_entities_comments_get.

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

Deploy Server

Other Tools