Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Add test case step by test case ID

add_test_case_step_by_id

Appends a new step to a Targetprocess Test Case using its test case ID, requiring step action text and expected result for clear test documentation.

Instructions

Add a new step to a Targetprocess Test Case. Despite tool name consistency, this takes testCaseId, not a step 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": {
      "testCaseId": "<testCaseId>",
      "description": "<description>",
      "result": "<result>"
    },
    "name": "add_test_case_step_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
resultYesExpected result for this step
testCaseIdYesTest case ID to append the step to (e.g. 145789)
descriptionYesStep action text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

B3.3/5.0
Behavior2/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, and it discloses very little. It implies a persistent mutation but says nothing about permissions, whether the step is appended at the end, ordering/index effects, or what is returned; the ID note is the only real behavioral hint.

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 short sentences, front-loaded with the action and resource, with the caveat placed immediately after where it is most useful. Nothing is wasted.

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 simple 3-required-param mutation with full schema coverage and no output schema, the description is enough to attempt a correct call. However, with zero annotations it omits the behavioral context (permissions, ordering, return behavior) that structured fields would otherwise supply.

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%, so all three parameters (testCaseId, description, result) are already documented in the schema, which puts the baseline at 3. The description reinforces the testCaseId trap but adds no new syntax, format, or ordering semantics beyond what the schema states.

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 ('Add a new step to a Targetprocess Test Case') and preempts the most likely misreading of the name by noting it takes a testCaseId rather than a step ID. That separates it from the update/delete step siblings, though it never explicitly contrasts with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the verb 'add' — an agent can infer this is for appending a step to an existing test case, but there is no explicit when-to-use vs update_test_case_step_by_id guidance, no stated prerequisites (e.g. the test case must exist), and no exclusions.

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