Skip to main content
Glama

ai_modeling_model_generate

Generate 3D models from text, images, multiview references, or batches, with optional PBR textures and face-count variations. Reuses a stable request_id so repeat calls return the original job.

Instructions

text / image / multiview / native image batch → 3D models; P2 supports face-count variations. 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>",
      "max_estimated_credits": "<max_estimated_credits>",
      "parameters": "<parameters>"
    },
    "name": "ai_modeling_model_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYes
request_idYes
max_estimated_creditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.6/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, openWorld=true, destructive=false), the description discloses that it consumes the caller's Studio account, that request_id provides idempotency, that a repeated request_id with changed input conflicts rather than overwriting, and that outcome_unknown must not be blindly retried. These are exactly the mutation-safety facts an agent needs and cannot get from the annotation flags.

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?

Three dense sentences, front-loaded with the capability and then the safety rules, with no filler. It leans on jargon ('P2', 'outcome_unknown') that is only decipherable from the schema, which is a small readability cost rather than wasted space.

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 purpose, auth, and idempotency for a complex open-world mutation, but with no output schema present it never says what is returned (e.g., a job handle and how to poll or inspect it) or how credit consumption relates to max_estimated_credits. For a tool this complex with no output schema, the description should close those loops.

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?

Top-level schema description coverage is 0%, and the nested parameters object exposes roughly twenty properties with no documented behavior for many of them. The description clarifies the mode axis, the role of request_id (stable/idempotent), and that variations are a P2 face-count feature, but it says nothing about the required max_estimated_credits cost ceiling or about the image-source field's 'front, left, back, right with null slots' ordering, leaving much of the low-coverage schema unexplained.

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 arrow notation 'text / image / multiview / native image batch → 3D models' names the resource (3D models) and the four input modalities, which map directly to the mode enum, so an agent can distinguish it from siblings like ai_modeling_image_generate or ai_modeling_texture_generate. The verb is implied by the name rather than stated ('generate'), which keeps it just short of a 5.

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?

Usage is implied by the modality list and by the retry rules ('reuse returns the original job', 'outcome_unknown must never be blindly retried'), which tell the agent how to call it safely. However, there is no explicit when-to-use/when-not guidance against the many sibling generation tools (image, texture, uv), so the agent must infer the boundary from the mode names alone.

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