Skip to main content
Glama
TestingBot MCP Server

TestingBot MCP Server

Official

updateTest

Update test metadata such as name, status, build, and extra attributes after execution to mark tests passed or failed and keep results organized.

Instructions

Update test metadata such as name, status (passed/failed), and other attributes. Useful for marking tests after execution.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "updateTest"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNew name for the test
buildNoBuild identifier
extraNoAdditional metadata (JSON string)
statusNoMark test as passed or failed
sessionIdYesThe session ID of the test to update

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

B3.1/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 for a mutation tool. It does not say whether the update is partial or replaces existing metadata, whether the session must already exist, what errors occur for an unknown sessionId, or whether the change is reversible — all material for a write operation.

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 with the resource and the updatable fields front-loaded, and no wasted wording. It is appropriately sized, though the second sentence adds little beyond the first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter mutation tool with no annotations and no output schema, the description should explain write semantics and the effect of omitting optional fields. It leaves the agent without enough to predict what a call does to existing test state.

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 every parameter is already documented in the input schema, including the status enum and the extra JSON-string field. The description only restates name and status and gestures at 'other attributes' without adding format or constraint detail, 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 (update) and resource (test metadata), then enumerates the updatable fields: name, status with passed/failed values, and other attributes. An agent can tell what the tool does, though the description never distinguishes it from siblings like deleteTest or getTestDetails.

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?

'Useful for marking tests after execution' gives an implied when-to-use context tied to post-run status reporting. There is no explicit guidance on when not to use it, no mention of prerequisites such as an existing sessionId, and no routing to alternatives.

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