Skip to main content
Glama

generate_status

Check the status of a 3D model generation job—waiting, running, done, or failed—and confirm when the model is downloaded and ready to import into Blender.

Instructions

Asks the provider once how a generate_start job is doing: waiting, running, done or failed. When it is done the model is downloaded (once, into the cache); then bring it into Blender with asset_import(source='rodin' or 'hunyuan', id=job, target_size=metres). Poll no more often than every 10 seconds.

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": {
      "job": "<job>"
    },
    "name": "generate_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

The annotations (readOnlyHint=false, openWorldHint=true) already signal an external call with side effects, and the description usefully explains that side effect: the model is downloaded once into the cache. It also discloses the single-poll, non-blocking semantics and the rate limit, so it adds context beyond the annotations. However, it does not describe what happens on a failed state or how to recover, so the disclosure remains partial.

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?

The description is a compact two-clause block that front-loads the core action and states the result states before the follow-up instructions. The parenthetical about the cache carries real information, so it earns its place; nothing is redundant.

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

Completeness4/5

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

Because there is no output schema, the description must describe return values, and it does so by listing the four possible states. The rate-limit and next-step details round out a simple one-parameter polling tool. The only gap is the lack of explicit guidance for non-terminal or failed states.

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 single 'job' parameter has 0% schema description coverage, so the description must carry the meaning. It does imply that job is the identifier of a generate_start job, and it shows the identifier being reused in the asset_import example (id=job), but it never explicitly defines the parameter's format or its source. That is partial compensation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Asks the provider once') plus a specific resource ('how a generate_start job is doing'), and it enumerates the possible states (waiting, running, done, failed). That distinguishes it clearly from generate_start, which launches the job.

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

Usage Guidelines4/5

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

The description gives explicit cadence guidance ('Poll no more often than every 10 seconds') and names the next step after completion (asset_import with source='rodin' or 'hunyuan', id=job, target_size=metres). It does not say when not to use it, nor does it distinguish it from the sibling 'status' tool, which leaves an ambiguity.

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