Skip to main content
Glama
Sign In
testit-mcp-server

testit-mcp-server

by iampopovich
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

restore_test_run

Idempotent

Restore an archived or deleted test run using its UUID to recover test execution records and make the run available again.

Instructions

Restore an archived (deleted) test run.

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

Input Schema

NameRequiredDescriptionDefault
idYesTest run UUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already disclose that this is a non-read-only, idempotent, non-destructive operation with open-world behavior. The description adds that the target must be an archived/deleted test run, but it does not explain what exactly is restored, whether prior results are preserved, or what happens if the run is not archived. These gaps are meaningful for a mutation tool, though the annotations cover part of the behavioral profile.

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?

The definition is a single front-loaded sentence with no waste. It states the action, resource, and relevant target state immediately.

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

Completeness4/5

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

For a simple one-parameter restore tool with full schema coverage and annotations covering safety and idempotency, the description is largely complete. It could say more about restoration semantics or permissions, but no output schema is needed and the core operation is clear.

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%, and the single 'id' parameter is already documented as a test run UUID. The description adds no syntax, format, or validation guidance beyond what the schema provides, so baseline 3 is appropriate.

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?

The description uses a specific verb ('Restore') and resource ('test run'), and clarifies the target state as archived/deleted. It does not explicitly distinguish itself from siblings such as delete_test_run or purge_test_run, but the action and object are unambiguous.

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?

The mention of 'archived (deleted)' implies that this tool is for reversing deletion rather than purging, which gives some usage context. However, it does not state when to choose this over delete_test_run or purge_test_run, nor does it list prerequisites such as required permissions or the expected state of the run.

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