Skip to main content
Glama
targetprocess-mcp-server

targetprocess-mcp-server

Update test case by ID

update_test_case_by_id

Update a Targetprocess Test Case by its ID, modifying only its name and description.

Instructions

Update a Targetprocess Test Case by its ID. Supports name and description 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_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTest case ID (e.g. 145789)
nameNoUpdated test case name
descriptionNoUpdated test case description (format as HTML or plain text)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.8.2

TDQS

A3.5/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 add real value by declaring the write is limited to name and description, which prevents attempts to set other fields, but it says nothing about whether omitted fields are left untouched, what permissions are required, whether changes are reversible, or what is returned.

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 with zero filler, and the scope limitation is front-loaded where an agent will see it before scanning parameters.

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 mutation tool with no annotations and no output schema, the definition covers identity and supported fields but omits partial-update semantics, failure modes (invalid ID), and result shape. Adequate to call correctly, but incomplete on behavior.

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%, so id, name, and description are already documented including an ID example and the HTML/plain-text note for description. The description adds only the confirmation that no other fields are accepted, so 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?

States a specific verb and resource ("Update a Targetprocess Test Case by its ID") and bounds the scope with "Supports name and description only." The resource is distinguishable from the step-level siblings by name, but the description never explicitly contrasts with update_test_case_step_by_id, so it stops short of full sibling differentiation.

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 implied rather than stated: an agent can infer this is the tool for renaming or re-describing a test case. There is no explicit when-to-use/when-not guidance and no pointer to update_test_case_step_by_id for step edits, which is the most likely confusion given the sibling set.

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