Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get release user stories with description

get_release_user_stories_with_description

Retrieve user stories for a specific release with their descriptions included, enabling detailed review without a separate lookup.

Instructions

Get release user stories with description in the response. Note: this is slower than "get_release_user_stories_names" tool, but if user wants to get descriptions, then this tool is the way to go.

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_user_stories_with_description"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesRelease name
withDescriptionYesInclude description in the response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A3.6/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 a genuine behavioral trait beyond the schema — that this call is slower than the names variant — which is useful for tool selection. However, it says nothing about permissions, result size or pagination, or how descriptions are truncated/formatted, all of which matter for an unannotated read tool returning verbose payloads.

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?

It is short and front-loaded, with the core purpose in the first clause and the tradeoff note immediately after. There is mild redundancy: 'with description in the response' restates the tool name, and the note repeats the same idea twice. Nothing extraneous beyond that.

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

Completeness4/5

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

For a two-parameter read tool with full schema coverage and no output schema, the description supplies what an agent most needs: what is returned (user stories plus descriptions) and the performance tradeoff for choosing it. Missing only secondary details such as authentication expectations or result-size characteristics, which are minor here.

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 parameters (name, withDescription) are already documented in the schema, making a baseline of 3 appropriate. The description adds no extra meaning about the release-name format or about why a withDescription flag exists on a tool that is defined by including descriptions. It neither compensates for nor detracts from 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 release user stories) plus a scope qualifier (descriptions included in the response), so an agent knows exactly what is returned. It also names a contrasting sibling, get_release_user_stories_names, which sharpens the distinction. It falls short of a 5 only because the phrase 'with description' largely echoes the tool name and the description does not clarify whether open/closed stories are included.

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

Usage Guidelines4/5

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

It gives explicit conditional guidance: use this one when the user wants descriptions, and it acknowledges the cost (slower) versus the names-only variant. That is real when-to-use and tradeoff information rather than implied usage. It does not address the other release-story siblings (e.g. get_release_open_user_stories) or state when this tool should not be chosen beyond the speed tradeoff.

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