testit-mcp-server

update_test_result

DestructiveIdempotent

Replaces an existing test result with a full PUT update, clearing any fields omitted from the request; use partial updates instead to preserve existing data.

Instructions

Replace a test result (PUT). WARNING: this is a full replacement — fields not sent (comment, message, links, step results...) are cleared. Prefer set_test_result for partial changes.

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_result"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Test result UUID.
`trace`	No
`comment`	No
`message`	No
`outcome`	No
`payload`	No	Raw TestResultUpdateV2Request fields; typed args take precedence.
`statusCode`	No
`durationInMs`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds the crucial behavioral detail that omitted fields are cleared, and enumerates examples (comment, message, links, step results). That is precisely the data-loss semantics an agent needs before making a destructive call, and it goes beyond what the annotations convey on their own.

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 the destructive warning front-loaded right after the verb phrase. Nothing is redundant and the alternative is placed last, where it is most useful.

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 destructive, open-world mutation with a nested payload object and no output schema, the description covers the safety story well but leaves individual parameter behavior and the interaction between typed args and payload under-explained. Adequate but with a clear gap on the 8-parameter surface.

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 only 25% and 8 parameters exist, so description carries some burden. It adds an important collective semantic (any parameter not supplied is wiped), but gives no individual meaning for trace, statusCode, durationInMs, or the payload escape hatch beyond what little the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Replace a test result (PUT)" gives a specific verb plus resource, and the parenthetical names the HTTP semantics. It is clearly distinguished from set_test_result by contrasting full replacement with partial changes.

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

Usage Guidelines5/5

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

Explicitly routes the agent to the alternative: "Prefer set_test_result for partial changes." Both the when-to-use (full replace) and when-not-to (partial change) conditions are stated, which is well above the minimum.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server