Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get user story comments

get_user_story_comments

Retrieve comments for a Targetprocess user story by its ID, with an optional limit on the number returned.

Instructions

Get comments for a TP user story 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_user_story_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTP user story 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

B3.3/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 behavioral burden. It implies a read-only fetch but says nothing about ordering, truncation when results is exceeded, behavior when the story has no comments, or permission requirements — meaningful gaps for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler; the verb, resource, and lookup key all appear before any padding.

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 two-parameter read tool with a fully documented schema, the core is covered, but with no output schema the description gives no hint of the return shape (comment text, author, timestamps), leaving an agent guessing about the response.

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 (e.g. 145789, 5-9 chars) and the results default of 25 are already documented. The description only restates 'by its ID' and adds no ordering or paging semantics beyond 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?

States a specific verb (Get) and resource (comments) scoped to a TP user story and keyed by ID. The 'user story' qualifier implicitly separates it from get_bug_comments and get_feature_comments, though it never names those siblings.

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

Usage Guidelines3/5

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

Usage is only implied by the name and description — read comments of a known user story. No explicit when-to-use, no prerequisites, and no mention of alternatives such as fetching content or bugs of the same story.

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