Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get not covered user stories in feature

get_not_covered_user_stories_in_feature

Retrieve user stories in a Targetprocess feature that are not covered by any tests by feature ID to identify testing gaps.

Instructions

Get user stories for a TP feature by its ID that are not covered by any tests

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

Input Schema

NameRequiredDescriptionDefault
idYesTP feature ID (e.g. 145636)

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 provided, so the description carries the burden. 'Get' implies a read-only operation, but the description says nothing about the return shape (a list, presumably), pagination, or what happens when the feature ID is invalid or has no uncovered stories.

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?

One sentence, front-loaded with the verb and resource, with the filter condition attached directly. No filler or redundant phrasing.

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 single-parameter read tool with no output schema, the description is nearly sufficient; the only minor gap is that it does not indicate the result is a list of user stories or describe failure behavior for an unknown feature ID.

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 'id' parameter is documented with a concrete example format, so the schema does the heavy lifting. The description only echoes 'by its ID' and adds no further semantics about the ID format.

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?

States a specific verb (Get), resource (user stories), and a scoping qualifier ('for a TP feature by its ID that are not covered by any tests'), which meaningfully separates it from the sibling get_feature_user_stories. It stops short of explicitly naming that sibling, so the differentiation is implied rather than stated.

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 'not covered by any tests' qualifier implies the use case (finding untested user stories), but there is no explicit when-to-use guidance, no mention of the alternative tool for all user stories, and no exclusions.

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