Skip to main content
Glama

AXIS Avatar Foundry

by com.jonathanarvay
OverviewDiscussionsAdmin

Generate 3D Avatar from Text (Paid)

generate_avatar_from_text

PAID (x402, 5 USDC): generate a production 3D avatar from a text prompt — xAI concept image → TRELLIS.2 GPU mesh → full canonical post-process (repair/validate/export). Payment settles ONLY when generation completes; a failed generation is never charged. Returns a job_id — poll with the free get_generation_status tool (typical runtime 5-15 minutes). Pass idempotency_key when a retry is possible (timeout/5xx) — replaying the same key returns the original job_id instead of a second GPU job/charge. [Paid: $5.00 USDC via x402 for unauthenticated calls on the hosted /mcp endpoint; DEFERRED settlement — charged only when the generation job completes, a failed job is never charged. Poll get_generation_status (free).]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesWhat to generate (subject description)
platformNoTarget engine (adds rigging + engine export)
asset_kindNoAsset taxonomy
polygon_tierNoQuality tier (defaults to the platform's configured tier)
texture_sizeNoTexture bake size in px (defaults per platform, else 2048)
idempotency_keyNoOptional caller-chosen dedup key (<=200 chars, [A-Za-z0-9_.:-]). Replaying the same key (per payer) returns the original job_id — no new GPU job, no new charge. Use on any retry after a timeout/5xx.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / asset_kind / enum
      Previous value: -[
-  "avatar",
-  "prop",
-  "vehicle",
-  "environment",
-  "vfx",
-  "weapon_armor",
-  "character_accessory",
-  "generic"
-]New value: +[
+  "avatar",
+  "prop",
+  "vehicle",
+  "environment",
+  "creature",
+  "weapon_armor",
+  "character_accessory",
+  "generic"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / idempotency_key
      Added value: +{
+  "description": "Optional caller-chosen dedup key (<=200 chars, [A-Za-z0-9_.:-]). Replaying the same key (per payer) returns the original job_id — no new GPU job, no new charge. Use on any retry after a timeout/5xx.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond annotations by disclosing the paid x402 model, deferred settlement (charged only on successful completion), and idempotency replay semantics. The idempotentHint=false annotation describes default behavior, which is consistent with the description's claim that idempotency only applies when a key is supplied, so there is no contradiction.

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?

The core deal terms are front-loaded, but the bracketed '[Paid: $5.00 USDC via x402 ...]' clause restates the opening 'PAID (x402, 5 USDC)' sentence almost verbatim, adding length without new information.

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?

Although there is no output schema, the description covers the return value (job_id), how to track progress, expected runtime, cost, and failure behavior. An agent has everything needed to invoke and follow up correctly.

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 coverage is 100%, so the baseline is 3. The description reinforces the significance of idempotency_key and mentions no new parameter syntax or defaults (e.g., polygon_tier/texture_size fallbacks) beyond what the schema already documents.

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 precise verb+resource ('generate a production 3D avatar from a text prompt') and describes the pipeline stages (xAI concept image → TRELLIS.2 mesh → post-process). It clearly differentiates from the sibling generate_avatar_from_image by specifying the text-driven path.

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 explicit downstream usage ('poll with the free get_generation_status tool', typical runtime 5-15 minutes) and a clear when-to-use rule for idempotency_key on retries after timeout/5xx. It never explicitly names generate_avatar_from_image as the alternative input mode, so the routing guidance is strong but not exhaustive.

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

All AXIS Avatar Foundry toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources