Skip to main content
Glama

ai_modeling_canvas_lab_job_cancel

Cancels an explicitly selected 3D Lab creative job using its job ID, stopping unwanted or mistaken generation tasks in Tripo Studio.

Instructions

Cancel an explicitly selected 3D Lab creative job.

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": {
      "jobId": "<jobId>"
    },
    "name": "ai_modeling_canvas_lab_job_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.7/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 description carries a lighter burden, yet it adds nothing beyond them. It says nothing about idempotency, whether already-completed jobs error, what happens to partial artifacts, or whether the cancel is synchronous — all material for a mutation.

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; nothing could be trimmed. However, its brevity reflects under-specification rather than disciplined density.

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?

The tool is simple and annotations cover the safety profile, but with no output schema the description should at least say what a successful cancel returns or how failures are signalled. Key operator questions about post-cancel state go unanswered.

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?

Only one parameter (jobId) exists and schema description coverage is 0%, so the description should compensate but does not. 'Explicitly selected ... job' vaguely points at jobId, but it never says the identifier comes from ai_modeling_canvas_lab_jobs nor explains the accepted character pattern.

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?

Specific verb (cancel) plus specific resource (3D Lab creative job), which distinguishes it from the sibling read tools like ai_modeling_canvas_lab_job_get. It does not differentiate from the other cancel siblings (ai_modeling_canvas_turn_cancel, ai_modeling_auth_cancel, ai_modeling_operation_cancel), so it stops short of a 5.

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?

The phrase 'explicitly selected' hints that the job must already be identified, but there is no statement of when to cancel versus poll (lab_job_get) or use a different cancel tool, and no preconditions such as job state. The agent must infer selection criteria entirely.

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