Skip to main content
Glama

generate_start

Start a paid 3D model generation job from a text prompt or images via Rodin or Hunyuan. The job and its credit cost are shown first, so nothing is sent or charged until you confirm.

Instructions

Starts generating a 3D model from text or pictures at a paid provider: rodin (Hyper3D Rodin; RODIN_API_KEY) or hunyuan (Tencent Hunyuan3D Pro; TENCENT_SECRET_ID and TENCENT_SECRET_KEY). Each job spends the provider's credits, so without accept_cost=True NOTHING is sent: the answer shows the job and its cost; ask the user before passing accept_cost=True. prompt (English or Chinese) or images (local .jpg/.png/.webp paths; rodin up to 5, hunyuan 1, and hunyuan takes a prompt or an image, not both). rodin: tier (default Gen-2.5-Low; Gen-2.5-Medium/High need a full API plan). hunyuan: pbr (PBR materials, +credits), face_count (3000 to 1500000, +credits). It takes minutes: poll generate_status, then asset_import(source=provider, id=job). Models are generated in the provider's cloud; the license is the provider's terms.

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": {
      "provider": "<provider>"
    },
    "name": "generate_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
pbrNo
tierNo
imagesNo
promptNo
providerYes
face_countNo
accept_costNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (which only declare it is not read-only and is open-world), the description discloses the credit-spend cost model, the dry-run confirmation gate, provider tier/plan restrictions, per-provider image count limits, the multi-minute latency, and that models live in the provider's cloud under the provider's license. This is exactly the behavior an agent cannot infer from structured fields.

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?

Cost gate is front-loaded and every sentence carries information, but the parenthetical provider interlude and the run-on hunyuan clause make it dense and harder to scan than it needs to be. No filler content, though; trimming would risk losing constraints.

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?

For a 7-parameter, cost-incurring, open-world tool with no output schema, the description supplies nearly everything needed: inputs, cost semantics, latency, and the next two calls. It stops short of saying what happens if neither prompt nor images is supplied, or how a returned job object is shaped, leaving a small edge case unexplained.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden and does: prompt language options, images as local .jpg/.png/.webp paths with per-provider limits, tier default and paid-plan requirement, pbr as a credit-incurring PBR-material flag, face_count range 3000–1500000, and provider enumerated with credential names. Only minor gaps remain (e.g. face_count default of 0 meaning 'provider default' is implied rather than stated).

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?

Opens with a specific verb and resource ('Starts generating a 3D model from text or pictures') and names the two concrete providers (rodin, hunyuan) with their credential env vars. An agent can distinguish this from generate_status and asset_import purely from the first sentence.

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 prerequisite ('without accept_cost=True NOTHING is sent... ask the user before passing accept_cost=True'), provider-specific input constraints ('hunyuan takes a prompt or an image, not both'), and the downstream workflow ('poll generate_status, then asset_import(source=provider, id=job)'). It covers when-to-use, when-not-yet, and the follow-up alternatives.

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