Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get test cases for TP UserStory card

get_user_story_test_cases

Fetches the Test Plan linked to a Targetprocess UserStory and returns its Test Cases using the supplied UserStory ID.

Instructions

Fetches a TP UserStory Linked Test Plan and fetches its Test Cases by provided card 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": {
      "resourceId": "<resourceId>"
    },
    "name": "get_user_story_test_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
resourceIdYesTP UserStory ID (e.g. 145789)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

B3.2/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 behavioral burden. It does disclose a genuinely useful internal behavior, namely that the tool resolves the Linked Test Plan and then retrieves Test Cases from it, which implies failure modes when no plan is linked. It stops short of stating permissions, error behavior, or whether steps are included, so it adds real but incomplete context.

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?

One sentence, front-loaded with the resource being retrieved, with no filler or redundant caveats. The repeated 'fetches ... and fetches' is slightly clumsy, but the double-fetch phrasing carries the meaningful two-step resolution, so it earns its words.

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 one-parameter read tool with no output schema and no annotations, the description covers the key structural complexity (indirection through a linked test plan). Missing are error conditions, an indication of what a returned test case looks like, and the distinction from the test-plan-ID siblings, which leaves a moderate gap.

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% and the single resourceId parameter already documents the TP UserStory ID format with an example. The description only echoes 'by provided card ID', adding no format, range, or validation meaning beyond the schema, which is the baseline case for full coverage.

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 concrete verb and resource: it fetches the Test Cases belonging to a TP UserStory card, and it reveals the indirect path (resolve the Linked Test Plan first, then its cases). The jargon ('TP UserStory Linked Test Plan') is dense, and it never contrasts itself with the sibling get_test_plan_test_cases_by_id, which takes a test plan ID directly, but the core action is unambiguous.

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 explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. An agent must infer from the name and the 'provided card ID' phrasing that this tool is the one for card-based lookups rather than test-plan-based ones, which is exactly the distinction a caller has to resolve.

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