Skip to main content
Glama
Sign In
tripo-studio-mcp

tripo-studio-mcp

by Neko-Yukari
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

tripo_animate

Applies animation to a rigged 3D model using a built-in preset, an existing motion asset, or a text prompt, then prepares an animated result for download.

Instructions

给已绑定的模型套动画（operation/retarget_model）。三选一：preset 用内置动作（不生成新动作）；motion_asset_id 复用已生成的动作；prompt 先用 motion/generate 文字生成动作（仅人形）。可选值用 tripo_list_motions 查。模型必须先 tripo_rig；取结果用 tripo_download 加 animated:true。

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": {
      "project_id": "<project_id>"
    },
    "name": "tripo_animate"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetNo内置动作名，如 walk / run / idle / dance_01；也可写全名 preset:biped:walk
promptNo文字生成动作，例如 walk forward slowly
rig_typeNo骨骼类型，默认取项目绑定时的类型
project_idYes
wait_secondsNo默认 480 秒
motion_asset_idNo复用已生成的动作资产
duration_secondsNo文字生成时的时长（秒），默认 5

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that preset does not generate a new motion, that prompt-generated motion is humanoid-only, and that the model must already be rigged. It does not say what happens to any pre-existing animation, nor does it explain the async/polling model implied by the 480-second wait default.

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-loaded with purpose, then the three modes, then prerequisites and retrieval — no wasted sentences. The semicolon-chained clauses and parenthetical operation names are dense and slightly harder to parse than necessary, but every clause carries information.

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 7-parameter mutation tool with no annotations and no output schema, the description covers the critical decision logic, prerequisites, and result retrieval. Remaining gaps — overwrite behavior, failure modes, and the polling/wait semantics — are modest given the schema's own coverage.

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 86%, so the schema already documents most parameters; the description's real contribution is the '三选一' mutual-exclusivity rule among preset, motion_asset_id, and prompt, plus the humanoid-only constraint on prompt, neither of which is expressible in the flat schema.

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 — apply an animation to an already-rigged model — and names the underlying operation (retarget_model). It clearly separates this from tripo_rig (which must run first) and from tripo_generate_text/motion generation, so an agent can pick it out of the 17-sibling list.

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 frames the three mutually exclusive modes (preset / motion_asset_id / prompt) and the constraint that prompt-based generation is humanoid-only. It also states the prerequisite (model must be rigged first via tripo_rig), where to discover valid values (tripo_list_motions), and how to fetch the result (tripo_download with animated:true).

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