Skip to main content
Glama

Cancel execution step

cancel_execution_step
Destructive

Cancel one step of a running platform execution (the twin of ankra cluster operations cancel-step) while the rest of the execution continues; only running, pending or blocked steps can be cancelled. Get the step ids from get_execution_details. A half-applied step can leave its resource between versions until the next reconcile; prefer cancel_execution when the whole operation is wrong.

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>",
      "step_id": "<step_id>"
    },
    "name": "cancel_execution_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
step_idYesStep id (UUID) from get_execution_details.
execution_idYesExecution id (UUID) from list_recent_executions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is known; the description adds the concrete consequence ('a half-applied step can leave its resource between versions until the next reconcile'), which is exactly the risk context annotations can't convey. It doesn't address whether a cancellation can be undone or what permissions are required, keeping it just short of 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: purpose and scope first, prerequisites second, risk and alternative last. The parenthetical reference to the internal CLI command ('the twin of `ankra cluster operations cancel-step`') is the one clause that doesn't help an agent choose or call the tool.

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 two-parameter mutation with no output schema, the description covers scope, eligibility constraints, id sourcing, side-effect risk, and the sibling alternative — essentially everything needed to call it correctly. Only the post-call outcome and reversibility are left implicit.

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 both fields already document their UUID source tools. The description's 'get the step ids from get_execution_details' restates the schema rather than adding format, constraints, or semantics beyond it, so the baseline 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 and resource ('Cancel one step of a running platform execution') and immediately scopes it against the sibling 'cancel_execution' by noting the rest of the execution continues. An agent can distinguish per-step cancellation from whole-execution cancellation without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit preconditions ('only running, pending or blocked steps can be cancelled'), tells the agent where to source the required ids ('get_execution_details'), and names the alternative with the condition that selects it ('prefer cancel_execution when the whole operation is wrong'). Both the when and the when-not are present.

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.