Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get user story bugs

get_user_story_bugs

Fetch the bugs linked to a Targetprocess user story by its ID to review defects impacting that story.

Instructions

Get bugs linked to 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_bugs"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTP user story ID (e.g. 145789)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

B3.2/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 disclosure burden. It implies a read but never states that it is read-only, whether closed/resolved bugs are included, pagination or result-size behavior, or what fields a returned bug carries.

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 and the scoping qualifier placed immediately after the verb. Brevity is appropriate, though a clause about return contents would have earned its place.

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?

A simple one-parameter read tool with no output schema needs little, and the description covers the core relationship. It is still thin on what comes back and on any filtering behavior, which matters for a bug-listing call.

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?

Only one parameter exists and schema coverage is 100% (the schema already gives format and example '145789'), so the baseline is 3. The phrase 'by its ID' confirms the identifier role but adds no format, range, or edge-case meaning 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?

The description states a specific verb and resource ('Get bugs') plus the linking scope ('linked to a TP user story by its ID'), which distinguishes it from sibling bug tools like get_release_bugs and list_my_bugs. It never names an alternative explicitly, so it stops short of a 5.

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 implied: call this when you have a TP user story ID and want its linked bugs. There is no explicit when-not guidance or named alternative for retrieving bugs by other scopes (release, current user, in-progress).

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