Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

native_job_cancel

Destructive

Cancels a queued operation by ID, preventing it from starting. Any native transaction already running finishes atomically, so partially applied geometry changes stay consistent.

Instructions

Cancel a queued operation. Running native transactions finish atomically.

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": {
      "operation_id": "<operation_id>"
    },
    "name": "native_job_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
operation_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing that cancellation only applies to queued work and that in-flight native transactions complete atomically. It does not say what happens when the operation_id is already running, already finished, or unknown.

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 short sentences with the action front-loaded and no filler. The second sentence is somewhat compressed and would read more clearly as a plain statement of what happens to running jobs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the destructive nature is covered by annotations. Still missing for a cancel mutation: error behavior for non-queued or unknown operations and the relationship to the sibling status and asset-job tools.

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 the single required parameter operation_id. The description never explains the identifier's origin (presumably from native_job_status) or format, so the schema's bare 'Operation Id' title is all the agent gets.

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?

The description names a specific verb and resource: 'Cancel a queued operation.' That is unambiguous about what the tool does. It stops short of distinguishing itself from the sibling asset_job_cancel, so an agent must infer the native/assets split from the tool name alone.

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 explicit guidance on when to call this versus asset_job_cancel or when to check state first via native_job_status. The only usage-adjacent statement is that running transactions are not interrupted, which is implied rather than stated as a precondition.

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