Skip to main content
Glama

TesterSwap

Cancel test

release_test
Destructive

Cancel your test before uploading an install screenshot, returning the held credits.

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": {
      "test_id": "<test_id>"
    },
    "name": "release_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
test_idYes

Output Schema

NameRequiredDescriptionDefault
stateYes
test_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds real value by naming the side effect (held credits are returned) and the precondition (before the install screenshot), but says nothing about whether the cancellation is reversible, what state the test ends in, or whether held credits are ever forfeited.

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?

One sentence, action first, no filler. The install-screenshot clause is a bit narrow and could read as the only valid moment to call it, but nothing is wasted.

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?

An output schema exists, so return values need not be explained, and the annotation set carries the destructive/non-idempotent profile. What is missing is the post-cancellation state of the test itself and the precondition for obtaining test_id, which matters for a destructive mutation.

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?

There is a single parameter (test_id) and schema description coverage is 0%, so the schema adds no meaning on its own. The description never references test_id or how to obtain it, though the parameter's role is strongly implied by 'your test' — a modest gap given only one obvious parameter.

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?

"Cancel your test" gives a specific verb and resource, and the added clause about returning held credits clarifies the effect in a way the name 'release_test' alone would not. It does not, however, distinguish this from siblings like reject_test or approve_test, so an agent still has to infer which cancellation path applies.

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?

It supplies one concrete timing condition — cancel before uploading an install screenshot — which is genuinely useful procedural context. Beyond that there is no statement of when to prefer this over reject_test or what happens if the window has passed, so guidance is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.