Skip to main content
Glama
Sign In

Voidless

by dev.voidless
OverviewDiscussionsAdmin

animate_3d_model

Animate a rigged 3D model. Either a ready-made move (free; characters: idle, walk, run, jump, attack, punch, kick, wave, hurt, death, cast, dance; four-legged animals: idle, walk, run, jump, attack, sit, hurt, death), a move copied from another of the user's rigged models (free: from_id + from_animation), or a description of any motion ('wag its tail', 'open the lid', 20 credits). Returns the clip, a GLB of the skeleton's motion that plays on the rigged model.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "animate_3d_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRigged 3D model asset ID
presetNoReady-made move id, e.g. 'walk' (free)
promptNoOr describe the motion, e.g. 'a spinning kick' (20 credits)
from_idNoCopy a move from this other rigged model (free)
durationNoWhole seconds (1-10), for a described motion (default: its natural length)
from_animationNoThe animation id on from_id to copy

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / duration / description
      Previous value: -"Seconds, for a described motion (default: its natural length)"New value: +"Whole seconds (1-10), for a described motion (default: its natural length)"
    • changedInput schema / properties / duration / type
      Previous value: -"number"New value: +"integer"
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare it is a non-read-only, non-destructive, non-idempotent, closed-world call; the description adds the material details an agent needs: the credit pricing tiers, the prerequisite that the model be rigged, and the return format (a clip plus a GLB of the skeleton's motion). It does not cover conflicting-parameter behavior or whether the clip is persisted onto the asset.

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?

A single dense sentence with parenthetical sub-lists; the primary action and the three modes are front-loaded, and the return value is appended last. Every clause carries information, though the nested parentheses make it slightly harder to scan than a short bulleted breakdown would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter generation tool with no output schema, the description covers all three invocation paths, pricing, prerequisites, and the shape of the return value. The remaining gaps (what happens if preset and prompt are both supplied, whether the clip is attached to the model) are minor rather than blocking.

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 schema already documents all six parameters, making 3 the baseline. The description does add value by listing the concrete preset vocabulary and splitting it by character versus four-legged animal, and by tying from_id together with from_animation as a pair, but duration and the preset/prompt exclusivity are left implicit.

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 and resource ('Animate a rigged 3D model') and then enumerates the three distinct modes of operation: preset move, copied move, and described motion. An agent can immediately tell this apart from rig_3d_model or animate_sprite based on the 'rigged 3D model' scope and the clip-returning behavior.

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 clear mode-selection guidance with cost consequences: presets and copied moves are marked free, while a described motion costs 20 credits, which effectively tells the agent when to prefer the cheap path. It stops short of naming sibling alternatives (e.g. animate_sprite, generate_animation_set) or stating exclusions, so it is strong context rather than explicit routing.

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

All Voidless 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