Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Delete test case step by ID

delete_test_case_step_by_id

Delete a Targetprocess test case step by ID to remove outdated or incorrect steps from a test case.

Instructions

Delete a Targetprocess Test Step by its 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": {
      "id": "<id>"
    },
    "name": "delete_test_case_step_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTest step ID (e.g. 145789)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden for a destructive mutation. It does not say whether deletion is permanent, whether it cascades to parent test cases or plans, what permissions are required, or what happens when the ID does not exist.

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 short, front-loaded sentence with no wasted words. It is arguably too terse rather than bloated, but structurally clean.

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, no-output-schema delete, the definition is minimally viable: the agent knows the action and the key. It is incomplete on irreversibility and side effects, which matter most for a destructive operation with zero annotation coverage.

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 format and an example, so the schema does the heavy lifting. The description only restates that the ID identifies the step and adds no format or lookup guidance beyond that.

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 uses a specific verb plus resource ('Delete a Targetprocess Test Step') and identifies the identifier used, so the action is unambiguous. It does not name a sibling or state how it differs from e.g. update_test_case_step_by_id, so it stops short of full differentiation.

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 guidance on when to use this versus update_test_case_step_by_id or the broader test-case deletion tools, and no stated preconditions. The only usage signal is the implicit pairing of 'delete' with an ID.

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