Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get feature user stories

get_feature_user_stories

Retrieves user stories linked to a Targetprocess feature by its ID, helping you inspect feature scope and related work items.

Instructions

Get user stories for a TP feature 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_feature_user_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTP feature ID (e.g. 145636)

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 provided, so the description carries the full behavioral burden, and it says almost nothing beyond the basic action. It does not disclose whether the response is paginated, what fields each user story contains, ordering, or any permission/scope constraints.

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?

The definition is one short, front-loaded sentence with no redundant wording. It is efficient, though its brevity borders on under-specification rather than pure conciseness.

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 single-parameter read tool with full schema coverage and no output schema, the description covers the minimum viable information. However, it lacks any hint about the shape of the returned collection, which matters for an agent deciding between this and the many other user-story retrieval tools.

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% and the single parameter is fully documented in the schema, including format and example. The description merely restates that the ID refers to a TP feature, adding no new syntactic or semantic detail. 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?

The description gives a specific verb and resource ('Get user stories for a TP feature') in a single clear clause. It is understandable in isolation, but it does not distinguish this tool from close siblings such as get_not_covered_user_stories_in_feature or the release-scoped user story tools.

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 guidance on when to use this tool instead of the many sibling tools that also return user stories. It states a lookup context ('by its ID') but offers no exclusions, prerequisites, or alternative routing.

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