Skip to main content
Glama

Cancel data run

cancel_data_run
Destructive

Cancel a running backup, restore or clone (the twin of ankra runs cancel). Work already finished stays finished; a cancelled capture leaves no complete restore point. Requires runs.operate and backups.operate.

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": {
      "run_id": "<run_id>"
    },
    "name": "cancel_data_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesRun id (UUID) from list_data_runs.

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?

Goes well beyond the annotations by disclosing the concrete destructive consequence ('a cancelled capture leaves no complete restore point') and the exact permission scopes required (runs.operate and backups.operate). It does not mention whether the cancellation is reversible or what status the run ends in, which keeps it below a 5.

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?

Three short sentences, front-loaded with the action and target, followed by consequences and then prerequisites. Every clause carries information an agent would otherwise have to guess.

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 one-parameter destructive tool with full schema coverage and no output schema, the description covers target, consequences and auth. It leaves out the post-cancel run state and the retry path, which would make the picture fully complete.

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 100% and the single run_id parameter is already documented in the schema as a UUID sourced from list_data_runs. The description adds no further meaning about the identifier, so the baseline of 3 applies.

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 (cancel) plus the exact resource scope (a running backup, restore or clone), which separates it cleanly from siblings like retry_data_run, get_data_run and list_data_runs. The parenthetical CLI equivalent further pins down intent.

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 word 'running' implicitly scopes usage, and 'Work already finished stays finished' tells the agent that cancelling a completed run is a no-op. However, it never names an alternative (e.g. retry_data_run for a failed run) or states an explicit when-not-to-use condition.

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.