Skip to main content
Glama

Canvas Stop Execution

aimixer_canvas_stop_execution
DestructiveIdempotent

Stop an attempt before provider acceptance, or cancel undispatched nodes of a prepared workflow by project_id and request_id. An accepted provider job may continue.

Input Schema

NameRequiredDescriptionDefault
attempt_idNo
project_idNo
request_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely new behavior: cancellation is best-effort and bounded to the pre-acceptance window, and it explains that only undispatched nodes are affected in workflow mode. That partial/no-op semantics is the main thing an agent could get wrong, and it is disclosed.

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?

Two sentences, no filler, with the primary action front-loaded and the important caveat placed last where it will be read. Dense but not padded; the only mild cost is jargon like 'prepared workflow' arriving without definition.

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 destructive, idempotent mutation with an output schema present, the description covers what it does, when it applies, and its critical limitation. The remaining gap is identifier provenance (where attempt_id/project_id/request_id come from), which is a real but modest omission.

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 0%, so all three parameters rely on the description for meaning. The text does convey the alternative pairing (attempt_id alone, or project_id plus request_id), which mirrors the schema's oneOf, but it never explains what an 'attempt' or a 'prepared workflow' is or how to obtain those identifiers.

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?

Uses specific verbs and resources: 'Stop an attempt before provider acceptance' and 'cancel undispatched nodes of a prepared workflow'. The two operational modes are stated explicitly, which lets an agent separate this from start_execution or prepare_execution, though no sibling is named outright.

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 condition for use ('before provider acceptance', 'undispatched nodes of a prepared workflow') plus the key exclusion that an accepted provider job may keep running. It stops short of naming which alternative tool to use when the job is already accepted, so it is strong context rather than a full routing rule.

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