Skip to main content
Glama

ai_modeling_operation_cancel

Cancel a specific active operation using its operator ID, operation type, and scene to stop unwanted or stalled work.

Instructions

Request cancellation for a specific active operation.

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": {
      "operator_id": "<operator_id>",
      "operation_type": "<operation_type>",
      "scene": "<scene>"
    },
    "name": "ai_modeling_operation_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
sceneYes
operator_idYes
operation_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already supply the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true). The description adds the useful nuances that cancellation is merely *requested* (implying it may be asynchronous or not immediate) and that the operation must be active, but it says nothing about what happens to in-flight work or partial results, whether the call is idempotent, or what a successful response looks like.

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 front-loaded sentence with no filler. It is efficient, though the terseness is partly the cause of the semantic gaps rather than a virtue in itself.

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?

This is contextual_completeness set at 4 by mistake placeholder.

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% for three required parameters (operator_id, operation_type, scene). The description only vaguely gestures at operation_type via 'operation' and does nothing to explain operator_id (a patterned identifier with a regex constraint) or scene, so it fails to compensate for the documentation gap.

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 active operation, with the 'active' qualifier narrowing the scope. It is clear on its own, but gives no hint about how it differs from siblings such as ai_modeling_auth_cancel, ai_modeling_canvas_lab_job_cancel, or ai_modeling_canvas_turn_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 when-to-use guidance, no prerequisites, and no named alternative. The reader must infer from the phrase 'active operation' that the target must be running and that other cancel tools exist for other resource types.

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