Skip to main content
Glama

ai_modeling_canvas_lab

Run 3D Lab instructions against explicitly attached assets with a stable request_id, so repeats return the original job instead of creating duplicate work.

Instructions

run a 3D Lab instruction against explicitly attached assets. Uses your Studio account and a stable request_id. Reuse returns the original job; changed input conflicts; outcome_unknown must never be blindly retried.

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": {
      "request_id": "<request_id>",
      "parameters": "<parameters>"
    },
    "name": "ai_modeling_canvas_lab"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYes
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare mutation, open-world behavior, and non-destructiveness. The description adds useful context beyond that: it uses the Studio account, requires stable request_id idempotency, returns the original job on reuse, and warns against blind retries after outcome_unknown.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action and followed by the most safety-critical idempotency details. There is no filler, and each sentence contributes operational value.

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?

The description covers account context and retry safety well, which are critical for an open-world mutation. It does not fully explain the return value for a new request, how to follow up on the job, or the nested node_id/prompt semantics, leaving some gaps for an agent invoking the tool.

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?

The description meaningfully explains request_id idempotency and reinforces that assets must be explicitly attached, which maps to asset_ids. It does not clarify the parameters object, node_id, prompt, or accept_variable_cost, so it only partially compensates for the low schema description coverage.

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 states a specific verb and resource: run a 3D Lab instruction against explicitly attached assets. This distinguishes the tool from planning or asset-binding siblings, though it does not explicitly name an alternative.

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?

It gives important operational guidance about stable request_id reuse, conflicting changed input, and never blindly retrying outcome_unknown. However, it does not explain when to use this run tool versus sibling tools such as lab_plan or lab_job_get.

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