Skip to main content
Glama
Sign In

Ludo AI Game Assets

by ai.ludo
OverviewDiscussionsAdmin

Animate 3D model

animate3DModel

Generate text-driven skeletal animations for an already-rigged 3D model. Pass the rigged GLB in model (URL or base64; the 3D asset file, not an AI model name) and a motion prompt (e.g. "walking", "swinging its axe"). The model must already have a skeleton - rig it first with rigModel if not. The job result is num_variants candidate animations (default 4), each a standalone animation-only GLB (skeleton + one clip, no mesh) in glb_url plus an mp4 preview_url, so you can pick the best one and fuse it with your model in a game engine or three.js. mode selects the representation - rot_trans (default, rotation plus translation per bone, most faithful) or rot_only (rotation only, easier to retarget onto another skeleton in an engine). Animation quality is hit-or-miss, which is why multiple candidates are returned. Credits are held once per call regardless of variant count and refunded if the job fails or is cancelled. Async generation job: returns {id, status} - poll getApiJob (job and credit contract: see the server instructions).

Credits: This endpoint consumes 0.5 credits per call.

Input Schema

NameRequiredDescriptionDefault
requestBodyYesPayload for animating a rigged 3D model from a text prompt

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / requestBody / properties / model / description
      Previous value: -"The already-rigged 3D asset to animate, as a URL or base64-encoded GLB file (not an AI model name). Rig it first with rigModel if it has no skeleton."New value: +"The already-rigged 3D asset to animate, as a URL or base64-encoded GLB file (not an AI model name). Rig it first with rigModel if it has no skeleton. Up to 30MB; a larger file is rejected with HTTP 400."
  2. Changed1 schema field changed
    • addedInput schema / properties / requestBody / description
      Added value: +"Payload for animating a rigged 3D model from a text prompt"
  3. Changed1 schema field changed
    • changedInput schema / properties / requestBody / properties / augment_prompt / description
      Previous value: -"Rewrite the prompt into a detailed motion caption with an LLM (recommended). Default: true."New value: +"Rewrites the prompt into a detailed motion caption with an LLM. Leave it on (the default). Turning it off does not give you more control - it usually gives worse results. Do not disable it unless you really know what you are doing and have tested your prompts extensively. Default: true."
  4. Changed2 schema fields changed
    • changedInput schema / properties / requestBody / properties / model / description
      Previous value: -"URL or base64-encoded already-rigged GLB to animate. Rig it first via the rig endpoint if it has no skeleton."New value: +"The already-rigged 3D asset to animate, as a URL or base64-encoded GLB file (not an AI model name). Rig it first with rigModel if it has no skeleton."
    • changedInput schema / properties / requestBody / properties / request_id / description
      Previous value: -"Optional client-provided identifier, unique per request. Re-sending the same request_id returns the existing job instead of generating again. Also usable with the results endpoint."New value: +"Optional client-provided identifier, unique per request. Re-sending the same request_id returns the existing job instead of generating again. Also usable as the request_id filter of listGenerations."
  5. Changed8 schema fields changed
    • removedInput schema / properties / requestBody / properties / augment_prompt / default
      Removed value: -true
    • changedInput schema / properties / requestBody / properties / augment_prompt / description
      Previous value: -"Rewrite the prompt into a detailed motion caption with an LLM (recommended)."New value: +"Rewrite the prompt into a detailed motion caption with an LLM (recommended). Default: true."
    • removedInput schema / properties / requestBody / properties / loop / default
      Removed value: -true
    • changedInput schema / properties / requestBody / properties / loop / description
      Previous value: -"Return to the initial pose: each clip plays forward then mirrors back to the rest pose for a seamless loop. Best for one-way motions (crouch, punch, wave); reads oddly for cyclic gaits like walking."New value: +"Return to the initial pose: each clip plays forward then mirrors back to the rest pose for a seamless loop. Best for one-way motions (crouch, punch, wave); reads oddly for cyclic gaits like walking. Default: true."
    • removedInput schema / properties / requestBody / properties / mode / default
      Removed value: -"rot_trans"
    • changedInput schema / properties / requestBody / properties / mode / description
      Previous value: -"Animation representation: rot_trans (per-bone rotation+translation, most faithful) or rot_only (rotation + root translation only, for retargeting)."New value: +"Animation representation: rot_trans (per-bone rotation+translation, most faithful) or rot_only (rotation + root translation only, for retargeting). Default: \"rot_trans\"."
    • removedInput schema / properties / requestBody / properties / num_variants / default
      Removed value: -4
    • changedInput schema / properties / requestBody / properties / num_variants / description
      Previous value: -"Number of candidate animations to generate; each returned as a standalone animation-only GLB with an mp4 preview."New value: +"Number of candidate animations to generate; each returned as a standalone animation-only GLB with an mp4 preview. Default: 4."
  6. Changed1 schema field changed
    • changedInput schema / properties / requestBody / properties / request_id / description
      Previous value: -"Optional client-provided id to retrieve the result later."New value: +"Optional client-provided identifier, unique per request. Re-sending the same request_id returns the existing job instead of generating again. Also usable with the results endpoint."
  7. Changed1 schema field changed
    • changedInput schema / properties / requestBody / properties / model / example
      Previous value: -"<url> OR data:image/png;base64,..."New value: +"<url> OR data:model/gltf-binary;base64,..."
  8. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, it discloses async job behavior, the {id, status} return shape, polling via getApiJob, credit hold/refund rules, a 30MB rejection limit, quality variance, and the exact output artifacts. This adds substantial operational context that annotations alone do not provide.

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

Conciseness5/5

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

The description is dense but front-loaded: it starts with the core action, then prerequisites, outputs, mode choice, quality expectations, credits, and async polling. Every sentence contributes operational or decision-relevant 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?

For a complex async generation tool with a nested request body and no output schema, the description covers the key prerequisite, input meaning, return shape, polling, credit behavior, and output artifact structure. Remaining parameter details such as loop and augment_prompt are fully documented in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3. The description still adds useful meaning by clarifying that model is a rigged GLB asset rather than an AI model name, explaining mode representations, and describing num_variants as candidate animation outputs.

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?

The description gives a specific verb and resource: generating text-driven skeletal animations for an already-rigged 3D model. It distinguishes the tool from rigModel by stating that rigging must happen first, and the 'text-driven' framing separates it from preset-based animation tools.

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?

It clearly states the prerequisite that the model must already have a skeleton and names rigModel as the alternative when it does not. It does not explicitly contrast with animate3DModelPreset or other animation transfer tools, so sibling routing is strong but not complete.

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

All Ludo AI Game Assets 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