Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get bug comments

get_bug_comments

Retrieve comments for a Targetprocess bug by its ID, with an optional results limit, to review discussion and context.

Instructions

Get comments for a TP bug by its ID

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": {
      "id": "<id>"
    },
    "name": "get_bug_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTP bug ID (e.g. 145789)
resultsNoNumber of comments to return, default is 25

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden, yet it discloses nothing beyond the retrieval target. It does not state ordering, whether the result is truncated to the default 25 with no indication of more comments, whether attachments or author metadata are included, or what permissions are needed.

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 redundant or filler wording. It is efficient, though the brevity is part of why the behavioral and usage gaps exist.

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?

For a simple read tool with two fully documented parameters and no output schema, the definition is minimally viable. The notable omissions are result-set behavior (truncation/ordering) and any hint about what a comment object contains, which no structured field covers.

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 both the ID format (5-9 chars, example 145789) and the results default of 25 are already documented in the schema. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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 names a specific verb and resource ("Get comments for a TP bug") and scopes retrieval to a single bug via its ID. The resource type implicitly separates it from siblings such as get_feature_comments and get_user_story_comments, though it never says so 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?

There is no when-to-use guidance, no conditions, and no mention of alternatives. An agent must infer from the resource name alone that this is the bug-scoped reader rather than the feature or user-story variant.

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