Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get release active user stories

get_release_open_user_stories

Retrieve open user stories for a Targetprocess release by name, excluding closed, done, passed, or ready-to-deploy items; optionally include descriptions.

Instructions

Get release active user stories (user stories that are not closed, done, passed, ready to deploy)

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>",
      "withDescription": "<withDescription>"
    },
    "name": "get_release_open_user_stories"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRelease name
resultsNoNumber of results to return, default is 50
withDescriptionYesInclude description in the response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A3.5/5.0
Behavior3/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; it does disclose the filtering semantics (which states count as inactive) and that a release scopes the result. It says nothing about result volume, pagination, ordering, or read-only/side-effect behavior, which for a zero-annotation tool leaves real gaps.

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 the scope qualifier immediately after the resource. No filler, no restatement of the title.

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 three-parameter read tool with full schema coverage and no output schema, the definition is workable but thin: it never confirms the read-only nature or mentions the release-name requirement. The filter definition is the main contribution and it is present.

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 the schema already documents name, results, and withDescription; the description adds no parameter meaning beyond it. 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 release active user stories') and defines 'active' inline as 'not closed, done, passed, ready to deploy', which removes most ambiguity. It does not, however, contrast itself with the sibling get_release_user_stories, so the boundary between 'active' and 'all' is left implicit.

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?

The parenthetical state filter implies when to reach for this tool (when only open work items matter), but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent must infer the tradeoff against get_release_user_stories on its own.

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