Skip to main content
Glama

Generate a 3D avatar

text_to_avatar

Generate a textured 3D avatar (GLB) from a text description or a reference image URL. Suited to characters and figures. Renders inline in an interactive 3D viewer. Use this when the user wants a character or figure generated from a text description or a reference image.

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": "text_to_avatar"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptNoDescription of the 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.

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. Changed1 schema field changed
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "description": "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.",
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and idempotentHint=false; the description adds useful non-annotation context such as the GLB output format and that results render inline in an interactive 3D viewer. The significant omission is that generation appears to be a job-based flow (idempotency_key mentions 'returns the original job'), yet the description never says the call is asynchronous or that check_job/get_job may be needed, which an agent needs to know to use results correctly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and readable, but the third sentence largely restates the first ('character or figure ... from a text description or a reference image'), and 'Suited to characters and figures' overlaps with it too. One of the three sentences could be cut without losing information.

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?

There is no output schema, so the description's note about GLB output and inline viewer rendering carries real weight, and it does that part. However, for a generative, job-producing tool with openWorld behavior, it omits what an agent most needs: whether the call is synchronous, how long generation takes, and how to retrieve or poll the result.

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%, including a detailed idempotency_key explanation, so the baseline is 3. The description confirms the two input modes (text description vs. reference image URL) but does not clarify that all three parameters are optional or whether at least one of prompt/image_url is needed, which is the main ambiguity the schema leaves open.

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 with the concrete artifact produced: 'Generate a textured 3D avatar (GLB) from a text description or a reference image URL.' The scope note 'Suited to characters and figures' helps separate it from generic mesh/forge siblings, but no sibling is named explicitly, so the differentiation stays implicit.

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 an explicit trigger condition: 'Use this when the user wants a character or figure generated from a text description or a reference image.' It does not say when NOT to use it, nor name alternatives such as forge_avatar or mesh_forge for other cases, leaving the agent to infer routing from sibling names alone.

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.