Skip to main content
Glama

ai_modeling_canvas_lab_job_get

Read-only

Retrieve a 3D Lab job by ID to inspect its status, generated artifacts, and observed charged credits for tracking and validation.

Instructions

Read a 3D Lab job, artifacts and observed charged credits.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the response includes artifacts and charged credits, which is useful context beyond annotations, but it says nothing about job lifecycle states, eventual consistency/polling behavior, or whether credits are settled or estimated.

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 short sentence with no filler, and the key resource is front-loaded. The phrasing is a compressed fragment ("Read a ... job, artifacts and observed charged credits") that reads slightly ambiguously, as if artifacts and credits were things being read rather than returned.

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?

For a simple one-parameter read with no output schema, the description is minimally viable: it signals the returned payload (artifacts + charged credits). It leaves out how to obtain the jobId and what job states mean, which an agent polling a job would want.

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?

One required parameter with 0% schema description coverage — the schema only supplies a regex pattern and length bounds, not meaning. The description never explains where jobId comes from (presumably an id returned when a lab job is created/planned) or how it relates to canvas/job identifiers used by siblings.

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 ("Read") and resource ("3D Lab job") and even names what comes back ("artifacts and observed charged credits"). It does not differentiate itself from the sibling list tool ai_modeling_canvas_lab_jobs or from ai_modeling_job_get, so an agent can't tell purely from the text whether this is the single-job fetch or something else.

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?

No when-to-use guidance: nothing says to call this after submitting/polling a lab job, nor how it relates to ai_modeling_canvas_lab_jobs (list) or ai_modeling_canvas_lab_job_cancel. Usage is only inferable from the name and the presence of a sibling cancel tool.

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