Skip to main content
Glama

Cancel execution

cancel_execution
Destructive

Cancel a running platform execution (a deploy, sync, or other operation from list_recent_executions). A mid-flight cancellation can leave the affected resource between versions until the next reconcile; prefer letting a deploy finish and rolling back unless it is actively harmful. Not running executions answer their settled state unchanged.

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": {
      "execution_id": "<execution_id>"
    },
    "name": "cancel_execution"
  }
}

Input Schema

NameRequiredDescriptionDefault
execution_idYesExecution id (UUID) from list_recent_executions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the bar is lower, yet the description adds real behavioral detail beyond them: a mid-flight cancellation can leave the resource between versions until the next reconcile, and executions that are not running simply answer their settled state unchanged. The warning about the resulting inconsistent resource state is exactly the non-obvious consequence an agent needs before invoking a destructive tool.

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 sentences, each doing distinct work: what it does, when to avoid it, and how settled executions respond. The purpose and the risk warning are front-loaded, with no restatement of the name or title.

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 single-parameter destructive tool with full annotation coverage and no output schema, the description covers purpose, risk, preferred alternative, and behavior on non-running executions. It does not say whether cancellation is immediate or blocking, nor what the caller receives back, which is a minor gap given no output schema exists.

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 parameter already documents that the execution_id is a UUID sourced from list_recent_executions. The description reinforces the provenance of the ID but adds no syntax, format, or validation detail beyond what the schema provides, so the baseline 3 applies.

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 ('Cancel a running platform execution') and enumerates what counts as an execution (deploy, sync, other operation from list_recent_executions). It implicitly separates itself from cancel_execution_step and cancel_agent_run by scoping to platform executions, but never names those siblings explicitly, so the differentiation is inferred rather than stated.

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?

Gives a clear decision rule: prefer letting a deploy finish and rolling back unless the execution is actively harmful. That is genuine when-to-use guidance with the alternative action named (rollback). It stops short of naming sibling tools like wait_for_execution, retry_execution, or cancel_execution_step as explicit alternatives.

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.