Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Get test case by ID

get_test_case_by_id

Retrieve a single Targetprocess Test Case by ID, returning its plain-text description and steps for quick review or validation.

Instructions

Get a single Targetprocess Test Case by its ID, including plain-text description and its 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_case_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTest case ID (e.g. 145789)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

B3.4/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; it does disclose what the response contains (plain-text description and steps), which is genuinely useful since there is no output schema. It does not state read-only semantics, error behavior for a nonexistent ID, or any permission requirements, so it adds partial but not rich behavioral context.

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 action and resource, followed by the useful detail about returned content. There is no redundant phrasing or padding.

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 one-parameter read tool with no annotations and no output schema, the description covers purpose and partial return shape, which is enough to call it correctly. A note on what happens for an invalid or missing ID would make it fully complete.

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 'id' parameter is documented with type, length bounds, and an example. The description's 'by its ID' adds no format or lookup semantics beyond what the schema already supplies, so the baseline of 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?

States a specific verb and resource ('Get a single Targetprocess Test Case by its ID') and adds the payload scope ('plain-text description and its steps'), which distinguishes it from the step-mutation and test-plan listing siblings. It does not name an explicit alternative, but the 'single ... by ID' framing makes the unit of retrieval 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 guidance, and no sibling is referenced. An agent must infer that this is the tool for a known test case ID rather than, say, get_test_plan_test_cases_with_steps_by_id, which could also surface steps.

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