Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get release user stories

get_release_user_stories

Retrieve user stories for a specified Targetprocess release by name, with an optional result limit. Use it to review release scope and included work.

Instructions

Get release user stories

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

Input Schema

NameRequiredDescriptionDefault
nameYesRelease name
resultsNoNumber of results to return, default is 50

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

C2.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 behavioral burden, and it discloses essentially nothing beyond the word 'Get' implying a read. It does not say whether results are paginated beyond the 'results' cap, whether the release must exist, or what a story record contains. It is not misleading, but it is behaviorally empty.

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

Conciseness2/5

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

It is short, but the single sentence merely echoes the title and therefore does not earn its place. Conciseness is not a virtue when the result is under-specification rather than density. There is no structure to speak of.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with two parameters, one required, no annotations, and no output schema, the description should explain scope and what is returned. Instead it leaves the agent unable to distinguish this from at least two similarly named siblings. Only the schema fields give any usable information.

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 coverage is 100%, with both 'name' (Release name) and 'results' (default 50) documented in the schema itself, so the baseline of 3 applies. The description contributes no additional meaning about valid release names or how the results limit behaves. The schema does all the work here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tautological: description restates name/title.

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 exclusions, and no mention of any alternative. An agent cannot tell from this text whether this returns all user stories or only some subset, nor when to prefer the '_open' or '_with_description' variants. Nothing is stated, only implied by the name.

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