Skip to main content
Glama

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.

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": {
      "mode": "<mode>",
      "model": "<model>"
    },
    "name": "generate_3d"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesWhich input the model is given.
modelYesA 3D model id from list_models.
promptNo
optionsNoModel-specific options; take the field names from list_models with include_inputs, and price them with estimate_cost first.
idempotency_keyNoReuse the same value when retrying this exact request.
expected_creditsNoThe 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

NameRequiredDescriptionDefault
modelYes
sceneYes
job_idYesPass to get_job to follow progress.
statusYespending and processing are running; success, partial, failed and canceled are final. 'partial' means some outputs finished and the rest were refunded.
dedupedYesTrue when an earlier call with the same idempotency key already started this job: nothing was charged again.
outputsYesHow many results this job makes.
media_typeYes
credits_chargedYesCredits taken from the balance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changed
    • removedOutput schema / properties / scene / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / scene / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. Changed1 schema field changed
    • 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"
      +}
  4. First observed

TDQS

A4.7/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 is asynchronous (returns a job id at once), that it spends credits, that a stale price aborts the call with a price_changed error carrying the new price, and that idempotency_key replays rather than double-bills. That is exactly the billing and retry context the idempotentHint/destructiveHint annotations do not carry.

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?

Front-loads the core action and return value, then sequences prerequisites (list_models, estimate_cost), the retry safeguard, and the follow-up call. Every clause carries actionable content; nothing is padding despite the four-sentence length.

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 six-parameter, async, credit-spending generation tool with a nested options object, the description covers the prerequisites, cost risk, retry semantics, and post-call follow-up. The return shape is covered by the existing output schema, so nothing essential is missing.

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, but the description adds real meaning: it maps each mode value to the input it consumes (prompt for text, options with the image URL for image, several view images for multiview, an existing model for model). The undocumented 'prompt' and nested 'options' parameters get contextual guidance that the schema text lacks.

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?

States a specific verb and resource ('Start a 3D generation') plus the immediate outcome ('return its job id at once'), then enumerates the five modes (text, image, multiview, sketch, model) so an agent knows the tool's full scope. This is far more than a restatement of the name.

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?

Gives strong procedural routing: fetch the model id and option names from list_models, price it with estimate_cost first because it spends credits, then follow with get_job. It does not address when to prefer the sibling 'generate' or start_batch instead, so the guidance is clear but not fully exclusive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources