Skip to main content
Glama

ai_modeling_model_animate

Apply preset or generated motion to a rigged 3D model using your Studio account. Handles request IDs safely so duplicate calls reuse jobs and unknown outcomes are not retried blindly.

Instructions

apply a preset or generated motion to a rigged model. Uses your Studio account and a stable request_id. Reuse returns the original job; changed input conflicts; outcome_unknown must never be blindly retried.

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": {
      "request_id": "<request_id>",
      "max_estimated_credits": "<max_estimated_credits>",
      "parameters": "<parameters>"
    },
    "name": "ai_modeling_model_animate"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYes
request_idYes
max_estimated_creditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already mark the tool as mutating (readOnlyHint=false) and non-destructive, so the description goes beyond them usefully. It discloses that the tool uses the caller's Studio account, that request_id provides idempotent reuse and conflicting-input handling, and that an outcome_unknown state must never be blindly retried. Those are real operational behaviors an agent could not infer from the annotations. It stops short of describing billing consequences of max_estimated_credits or what the returned job object looks like.

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?

Three short sentences with the core action front-loaded and no filler. The telegraphic fragments ('changed input conflicts', 'outcome_unknown') are dense but functional. The only cost is that the phrasing is clipped enough to need a second read.

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

Completeness3/5

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

For a mutating tool with a nested parameters object, no output schema, and no annotation coverage of idempotency, the description covers the essential contract (auth, request_id reuse, retry safety). It leaves meaningful gaps: how max_estimated_credits is enforced, when to supply animation versus motion_asset_id, and what an agent receives back from the job. A caller would still need to guess at several call-shaping decisions.

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?

The schema has almost no textual descriptions (0% coverage), so only its patterns and the rig_type enum hint at parameter meaning. The description compensates for exactly one parameter, request_id, whose idempotency contract it explains well. It adds nothing about max_estimated_credits (a credit ceiling), the animation preset string format, or the distinction between motion_asset_id and animation, leaving the remaining parameters to be inferred from regexes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: apply a preset or generated motion to a rigged model. That phrase also communicates the prerequisite of an already-rigged model, which separates it from rigging and generation siblings. It does not explicitly name which sibling to use for removal or generation, but the scope is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The definition implies when to use the tool, namely when a rigged model exists and a preset or generated motion must be applied, and it strongly guides retry behavior via the request_id semantics. It gives no explicit guidance about when NOT to use the tool or how it compares with alternatives such as ai_modeling_animation_remove or ai_modeling_model_generate. So the usage guidance is useful but partly inferred.

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

Deploy Server

Other Tools