AI3D Studio

Generate a 3D model

generate_3d

Start a 3D generation and return its job id at once. mode picks the input: text (prompt), image (options with the image URL), multiview (several view images), sketch, or model (edit an existing 3D model). Take the model id and its option names from list_models, and check the price with estimate_cost first: this spends credits. Pass a stable idempotency_key when retrying so a retry replays the same job instead of billing twice. Then call get_job to follow it.

Input Schema

Name	Required	Description
`mode`	Yes	Which input the model is given.
`model`	Yes	A 3D model id from list_models.
`prompt`	No
`options`	No	Model-specific options; take the field names from list_models with include_inputs, and price them with estimate_cost first.
`idempotency_key`	No	Reuse the same value when retrying this exact request.
`expected_credits`	No	The credits estimate_cost answered for this request. If the price has moved since, nothing is started or charged and the error (price_changed) gives the new price.

Output Schema

Name	Required	Description
`model`	Yes
`scene`	Yes
`job_id`	Yes	Pass to get_job to follow progress.
`status`	Yes	pending and processing are running; success, partial, failed and canceled are final. 'partial' means some outputs finished and the rest were refunded.
`deduped`	Yes	True when an earlier call with the same idempotency key already started this job: nothing was charged again.
`outputs`	Yes	How many results this job makes.
`media_type`	Yes
`credits_charged`	Yes	Credits taken from the balance.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026
- removedOutput schema / properties / scene / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / scene / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedOct 20, 2026

addedInput schema / properties / expected_credits

Added value: +{
+  "description": "The credits estimate_cost answered for this request. If the price has moved since, nothing is started or charged and the error (price_changed) gives the new price.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

First observedOct 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, it discloses that the call spends credits, that credits are only committed after a successful start, that a stale price aborts with a price_changed error and nothing is charged, and that idempotency_key prevents double billing. That is exactly the cost/irreversibility context an agent needs before firing a mutating, credit-consuming request. The lack of inherent idempotency (idempotentHint=false) is consistent with the guidance to supply a key rather than a contradiction.

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?

Purpose and immediate return value are front-loaded, followed by mode semantics, then prerequisites, then the safety rule and the follow-up call. Every sentence carries operational information and none is redundant.

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

Completeness5/5

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

For a credit-spending, asynchronous, nested-options tool with 6 parameters, the description covers input interpretation, cost verification, retry safety, error behavior, and the polling hand-off to get_job. With an output schema present, it does not need to describe the returned job id further.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 83%, so the baseline is 3; the description earns above that by explaining the semantic of each mode value and by tying expected_credits to the estimate_cost/price_changed flow. It still leaves the shape of `options` to list_models rather than describing any common fields, so it does not fully compensate for the remaining gap.

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 resource plus the async contract: 'Start a 3D generation and return its job id at once.' It also enumerates what each mode consumes (text prompt, image URL, view images, sketch, existing model), so an agent knows exactly what the tool produces. It does not differentiate itself from the sibling `generate` tool, which prevents a clean 5.

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

Usage Guidelines5/5

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

Gives an explicit sequence: pick a model id and option names from list_models, price it with estimate_cost, then call get_job to follow progress. It also states a conditional rule for retries (pass a stable idempotency_key) and warns that this call spends credits, so prerequisites and hand-offs are all spelled out.

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

All AI3D Studio tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?