Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

asset_job_cancel

Destructive

Cancel the server-owned Blender worker group for a specified operation ID to stop incomplete asset outputs and invalidate partial results.

Instructions

Cancel only this server-owned Blender worker group; incomplete outputs are invalid.

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": "asset_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.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one genuinely new behavioral fact — that incomplete outputs from a cancelled group are invalid and must not be used — but does not say whether cancellation is graceful or forced, or what happens to already-produced artifacts.

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 compact sentence with the scope constraint front-loaded and no filler. The trailing clause "incomplete outputs are invalid" is terse to the point of ambiguity about what the agent should do with such outputs.

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. However, for a destructive, non-idempotent mutation the description omits what is actually terminated, whether partial artifacts are cleaned up or merely marked invalid, and whether a cancelled operation can be retried.

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 0% and there is exactly one required parameter, operation_id, which the description never mentions. The description does not clarify whether operation_id identifies the job group to cancel, the cancellation request, or something else, so it leaves the only parameter's meaning to the bare schema title.

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 a narrowly scoped resource: "Cancel only this server-owned Blender worker group." The "server-owned" qualifier implicitly separates it from native_job_cancel, but the sibling is never named, so the agent must infer the distinction.

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

Usage Guidelines3/5

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

The word "only" plus "server-owned" implies a usage boundary (do not use for non-server-owned jobs), but the alternative tool is not named and no prerequisite conditions (job must be in-flight, operation_id must reference an active group) are given. Usage is implied rather than stated.

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