Skip to main content
Glama

Generate a rigged, animation-ready avatar

forge_avatar

Generate a rigged, animation-ready 3D avatar (GLB) from a single text prompt or a reference image, in one step. Generates the mesh, then auto-rigs it with a humanoid skeleton so it is ready to pose and animate. Made for characters; objects are steered to the mesh generator. Renders inline in an interactive 3D viewer. Use this when the user wants a posable, animation-ready character in one step instead of generating then rigging.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "forge_avatar"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptNoDescription of the character/avatar to generate.
image_urlNoOptional http(s) URL to a reference image to reconstruct in 3D.
idempotency_keyNoOptional: any string you choose (up to 200 characters) that names this one generation, such as a task id. Calling again with the same key within 24 hours returns the original job instead of starting a new one, so a retry after a timeout never generates twice. Use a new key for a new model.
allow_non_humanoidNoSet true to rig a non-humanoid subject anyway (rigging assumes a humanoid figure).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Optional retry key. Send the same key again (same caller, same arguments, within 24 hours) and you get the original job back instead of a second generation, so a retry after a timeout cannot burn quota twice. Use a fresh key for each distinct request. A failed attempt is not remembered, so its key can be reused."New value: +"Optional: any string you choose (up to 200 characters) that names this one generation, such as a task id. Calling again with the same key within 24 hours returns the original job instead of starting a new one, so a retry after a timeout never generates twice. Use a new key for a new model."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the pipeline (mesh generation followed by auto-rigging with a humanoid skeleton), the return artifact (GLB, rendered inline in an interactive 3D viewer), and the humanoid assumption behind rigging. It does not disclose latency/cost or whether the call blocks versus returning a job, which matters given the openWorldHint=true generation backend and the idempotency_key's reference to a 'job'.

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?

Front-loaded with the verb, output format, and the one-step value proposition, and every sentence carries routing or behavioral content. There is mild redundancy — 'rigged, animation-ready' and the 'in one step' framing are each restated in the first and last sentences — but no filler.

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?

With no output schema, the description does cover the return artifact (GLB in an inline 3D viewer) and the rigging caveat, which is the core of what an agent needs. It omits whether this is an async job requiring check_job/get_job follow-up (the idempotency_key parameter hints at jobs but the description never says so), and leaves the prompt-vs-image relationship open, so it is adequate but not complete for a generation tool.

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?

Schema description coverage is 100%, so the parameters are already well documented and the baseline is 3. The description adds only that both prompt and image input exist and that the tool assumes a humanoid figure (relevant to allow_non_humanoid); it never clarifies whether prompt and image_url are alternatives or can be combined, which is the one semantic point an agent would still need.

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 ('Generate a rigged, animation-ready 3D avatar (GLB)') plus the two input modes (text prompt or reference image), and the phrase 'in one step ... instead of generating then rigging' implicitly separates it from the text_to_avatar + rig_mesh path. An agent can tell this apart from its siblings without opening any schema.

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 a clear when-to-use condition ('user wants a posable, animation-ready character in one step instead of generating then rigging') and a positive exclusion ('Made for characters; objects are steered to the mesh generator'). The alternatives are described behaviorally rather than named, so the routing is slightly less direct than naming mesh_forge or rig_mesh explicitly, but the guidance is unambiguous.

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.