Skip to main content
Glama

ai_modeling_canvas_turn_cancel

Cancel a selected creative turn by its turn ID to halt an in-progress Canvas generation or edit.

Instructions

Cancel an explicitly selected creative turn.

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": {
      "turnId": "<turnId>"
    },
    "name": "ai_modeling_canvas_turn_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
turnIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the bar is lower. Still, the description says nothing about what state the turn is left in after cancellation, whether the operation is reversible, or what preconditions must hold for 'explicitly selected' to be true.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

A single short sentence, so nothing is wasted and the core action is front-loaded. The problem is under-specification rather than verbosity, leaving the definition too thin to be actionable.

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 mutation-style cancel operation with no output schema and an undocumented required identifier, the description should explain prerequisites and side effects. Neither is present, so an agent cannot confidently confirm it is invoking the correct cancellation tool.

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?

There is exactly one parameter (turnId) with 0% schema description coverage, and the description never explains what a turn identifier is or where to obtain it. The description therefore does not compensate for the documentation gap in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (cancel) and a resource (creative turn), so the basic action is identifiable. However, the qualifier 'explicitly selected' is ambiguous and does not distinguish this tool from sibling cancel tools such as ai_modeling_canvas_lab_job_cancel, ai_modeling_auth_cancel, or ai_modeling_operation_cancel.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the other cancel variants or versus ai_modeling_canvas_turn_get / ai_modeling_canvas_continue. The phrase 'explicitly selected' implies a precondition but never states it, and no exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools