Skip to main content
Glama

Cancel Service Run

sandbase_run_cancel
Destructive

Request cancellation of an Agent Service run; inspect its status afterward.

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": {
      "service_id": "<service_id>",
      "run_id": "<run_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "sandbase_run_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes
service_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, openWorldHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds real value by framing this as a cancellation *request* that may not take effect immediately, but it omits what happens to in-flight work, whether the run is terminated or just flagged, and required permissions.

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?

A single tight sentence with the primary action front-loaded and the follow-up guidance second; nothing is redundant. It is arguably too terse for the information an agent needs, but that is a completeness problem, not a verbosity one.

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 destructive, non-idempotent mutation with no output schema and zero parameter documentation, the description should explain side effects, the meaning of idempotency_key, and what the cancellation response indicates. It covers only the bare action and a follow-up hint, leaving the agent under-equipped to call it safely.

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 description coverage is 0% across three required parameters (service_id, run_id, idempotency_key), so the description must carry the full burden and adds nothing — not even what idempotency_key does or how it interacts with idempotentHint=false. Only the loose association of run_id with 'run' is inferable from the description.

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 and resource ('Request cancellation of an Agent Service run'), which clearly separates it from sandbase_run (start) and sandbase_run_get (inspect). The word 'request' signals the operation is a cancellation ask rather than a guaranteed immediate stop.

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 clause 'inspect its status afterward' implies a follow-up with a status tool such as sandbase_run_get, which is useful sequencing guidance. However, there is no explicit when-to-use vs. when-not, no prerequisites (e.g. run must be active), and no statement about what to do if the run already finished.

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.