Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Update test case step by ID

update_test_case_step_by_id

Update a Targetprocess test step by ID to revise its action text or expected result, keeping test case steps accurate and current.

Instructions

Update a Targetprocess Test Step by its ID. Supports description and result only.

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": "update_test_case_step_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTest step ID (e.g. 145789)
resultNoUpdated expected result for this step
descriptionNoUpdated step action text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

B3.2/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. It does disclose a valuable constraint, that only description and result are mutable, but it says nothing about permissions, what happens to unmentioned fields, whether the change is reversible, or what the response contains. For a mutation tool with zero annotation coverage this leaves significant gaps.

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?

Two short sentences, purpose-first, with the scope limitation attached immediately rather than buried. No filler or redundant phrasing.

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?

A simple 3-parameter mutation tool with a fully documented schema, so the description does not need to explain parameters. It is still thin for a write operation with no annotations and no output schema: nothing about the outcome of a successful update or how partial input is treated.

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 the schema already documents id, result, and description with examples and length bounds. The description's only added semantics is the reminder that these two fields are the whole update surface, which mildly reinforces but mostly restates the schema. 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?

Names a specific verb and resource ('Update a Targetprocess Test Step by its ID') and adds a scope constraint ('Supports description and result only') that separates it from add/delete test-case-step siblings. It stops short of naming the sibling that handles other field updates, so it is clear but not fully sibling-differentiated.

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: the 'by its ID' framing and the field whitelist tell an agent this is the edit path for an existing step's action text and expected result. There is no explicit statement of when to prefer this over update_test_case_by_id or what preconditions (step existence, permissions) must hold.

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