Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get test plan test cases by ID

get_test_plan_test_cases_by_id

Retrieve all test cases for a Targetprocess test plan by ID, including cases in nested child plans and containers, with IDs, names, descriptions, and plan metadata.

Instructions

Get test cases belonging to a Targetprocess Test Plan by plan ID, including cases in nested child test plans/containers. Returns id, name, plain-text description, and containing test plan metadata (no 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_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

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does disclose meaningful behavior: recursive inclusion of nested child plans/containers and the exact return shape (id, name, plain-text description, containing plan metadata, no steps). It does not mention pagination, result limits, or permission requirements, which leaves a gap for a read tool with no annotations.

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?

Two compact sentences that front-load the operation and scope before the return-shape detail. Every clause carries information an agent needs; nothing is padding.

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

Completeness5/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, the description supplies the return fields, the nested-scope behavior, and the exclusion of steps. That covers everything an agent needs to select and invoke it correctly.

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 parameter already has a description and example ('Test plan ID (e.g. 145789)'). The description only restates 'by plan ID' and adds no format, lookup, or constraint guidance beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource pair (get test cases belonging to a test plan) scoped by plan ID, and adds the non-obvious detail that nested child plans/containers are included. The parenthetical '(no steps)' cleanly separates it from get_test_plan_test_cases_with_steps_by_id without naming it.

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?

The phrase '(no steps)' tells an agent when this tool is insufficient and implicitly points to the with-steps sibling, and 'including cases in nested child test plans/containers' sets expectations about scope. It stops short of explicitly naming the alternative or stating exclusions, so it lands just below a 5.

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