AXIS Avatar Foundry

Generate 3D Avatar from Image (Paid)

generate_avatar_from_image

PAID (x402, 6 USDC): generate a production 3D avatar from a reference photo (base64) — xAI A-pose normalize → TRELLIS.2 GPU mesh → full canonical post-process. 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: $6.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

Name	Required	Description
`prompt`	No	Optional style/subject hint alongside the image
`platform`	No	Target engine (adds rigging + engine export)
`image_b64`	Yes	Base64-encoded reference image (PNG/JPEG)
`asset_kind`	No	Asset taxonomy
`polygon_tier`	No	Quality tier (defaults to the platform's configured tier)
`texture_size`	No	Texture bake size in px (defaults per platform, else 2048)
`idempotency_key`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

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"
+]

Changed1 schema field changedAug 27, 2026

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"
+}

First observedAug 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond annotations by disclosing cost ($6 USDC via x402), deferred settlement behavior (charged only on completion, failed jobs never charged), expected runtime, and dedup semantics. This is exactly the payment/authorization context an agent needs before invoking an expensive GPU 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-loads price and purpose, but wastes space with a bracketed paragraph that repeats the x402 cost, settlement, and polling guidance already stated in the first two sentences. Otherwise tight.

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?

With no output schema, the description correctly states the return value (job_id) and the follow-up polling tool, plus cost and failure semantics. Nothing essential for correct invocation is missing.

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 every parameter is already documented in the schema; the description largely restates idempotency_key behavior rather than adding new semantics. Baseline 3 applies when the schema carries the parameter burden.

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+resource ('generate a production 3D avatar from a reference photo') and names the concrete pipeline steps (normalize → TRELLIS.2 mesh → post-process). It is clearly distinguishable from the sibling generate_avatar_from_text since the input modality (photo/base64) is named.

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?

Explicitly routes the agent to get_generation_status for polling, states the typical runtime, and prescribes when to pass idempotency_key (retry after timeout/5xx). When-to-use and the follow-up tool are both spelled out.

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 tools Inspect

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

Need Help?