Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get test plan test cases with steps by ID

get_test_plan_test_cases_with_steps_by_id

Retrieves all test cases for a Targetprocess Test Plan by ID, including nested child plans and containers, plus each test case's steps.

Instructions

Get test cases belonging to a Targetprocess Test Plan by plan ID, including nested child test plans/containers and each test case steps.

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

Input Schema

NameRequiredDescriptionDefault
idYesTest plan 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?

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: the result recurses into nested child test plans/containers and expands each test case's steps. It does not say whether nested containers are flattened or returned as a hierarchy, nor anything about volume, pagination, or permissions for a potentially large recursive read.

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 front-loaded sentence with no filler; the key scope detail (nested containers + steps) arrives immediately. Minor grammar awkwardness ('each test case steps') is the only blemish.

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 single-parameter read with no output schema and no annotations, the description should convey more about the returned shape. It tells the agent what is included (test cases, steps, nested containers) but not how that nesting is represented in the response, leaving a real gap for downstream consumption.

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?

Single parameter with 100% schema description coverage; the schema already states the plan ID format and example. The description only restates that lookup is by plan ID, adding no format or constraint detail beyond the schema, so 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 names a specific verb (Get) and resource (test cases belonging to a Test Plan) and pins the lookup key to plan ID. The clause about including nested child test plans/containers and each test case's steps effectively distinguishes it from the sibling get_test_plan_test_cases_by_id, though it never names that sibling.

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 guidance and no alternative tool is named. An agent must infer from the 'with steps' phrasing that this is the deeper/recursive variant versus the flat sibling, which is a reasonable but unstated inference.

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