Skip to main content
Glama

DECA Labs

Cancel a test

cancel_test
DestructiveIdempotent

Cancel a test that is still in review, before its ads run. The whole budget is refunded to the paying wallet.

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

Input Schema

NameRequiredDescriptionDefault
idYes
access_tokenNoNeeded when the test was paid without a key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true, and readOnly=false, so the mutation profile is covered. The description adds genuinely new behavior: the entire budget is refunded to the paying wallet, which is critical financial context an agent would not otherwise know. It does not disclose the error/response shape when cancelling an ineligible test.

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, the operation and its precondition front-loaded, and the refund consequence immediately after. No filler or redundant restatement of the title.

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, two-parameter mutation with no output schema, the description covers the key outcome (full refund) and the eligibility window, which is a solid core. However, it leaves the `id` parameter undefined, gives no guidance on the required access_token, and does not say what happens if the test is not in review, leaving real gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: access_token is documented in the schema, but `id` is unexplained there. The description mentions neither parameter — not the id format (test id) nor when the access_token is required — so it does not compensate for the coverage gap.

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?

States a specific verb and resource ('Cancel a test') plus a scope condition ('still in review, before its ads run') that immediately distinguishes it from siblings like start_test and get_test. An agent can tell exactly what operation this performs without opening the schema.

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

Usage Guidelines4/5

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

The phrase 'that is still in review, before its ads run' gives a clear eligibility condition for when this tool applies, implicitly excluding tests that are already running or completed. It stops short of naming alternatives (e.g. what to call for a running test) or stating the failure behavior when the precondition is not met.

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.

Resources