axis_processRun the full AXIS avatar pipeline (classify → normalize → rig → skin → validate). Returns contract summary. [Paid: $1.50 USDC via x402 for unauthenticated calls on the hosted /mcp endpoint; settled only on a successful (non-error) result.]
| Name | Required | Description | Default |
|---|---|---|---|
| export | No | Also export to the target platform | |
| platform | No | Target platform | |
| file_path | Yes | Path to mesh file |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value by disclosing the payment requirement ($1.50 USDC) and the fact that it settles only on successful results, which is critical behavioral context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise: two sentences effectively cover purpose, pipeline steps, return type, and billing. The first sentence is front-loaded with the core action, and the second adds necessary operational context without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description provides sufficient context for a complex pipeline tool, including the pipeline stages and payment terms. It does not explain the contents of the contract summary, but the schema covers parameters and annotations cover safety. Overall, adequately complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema provides full descriptions for all three parameters (file_path, export, platform) with 100% coverage. The description does not add parameter-level details beyond what the schema already offers, so the baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool runs the full AXIS avatar pipeline with specific steps (classify → normalize → rig → skin → validate) and returns a contract summary. This distinguishes it from sibling tools like axis_validate (which only validates) and axis_export (which only exports).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description conveys when to use the tool: to execute the complete pipeline rather than individual steps. However, it does not explicitly mention alternatives or scenarios where other tools should be preferred, though the 'full pipeline' wording implies it includes sub-steps.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool occupies a clearly distinct role: generation (image/text) plus status polling, pipeline processing (file vs inline), validation, repair, export, compliance, manifest verification, inspection, comparison, capabilities, and animation retargeting are all separated. The only potential overlap between axis_process and post_process_mesh is explicitly resolved by input method and scope.
Two naming styles coexist: axis_* prefix for core pipeline/contract tools and descriptive non-prefixed names for generation, repair, and compliance tools. Within axis_*, the verb/noun order is inconsistent (e.g., axis_manifest_verify vs axis_list_capabilities), making the set readable but not uniform.
14 tools is squarely within the ideal 3-15 range and matches the broad but well-defined scope of a full avatar foundry: generation, processing, validation, repair, export, compliance, and metadata inspection. Every tool serves a necessary function with no redundancy or bloat.
The toolset covers the full lifecycle from generation (image/text) and status polling through post-processing, repair, validation, export, and Roblox-specific compliance. Minor gaps exist, such as no tool to list available animation clips (retarget_animation references 'built-in' clips) or manage a library of previously generated avatars, but core workflows are fully supported.