Skip to main content
Glama

tripo_list_motions

Lists available motions by rig type, including generated motion assets reusable via motion_asset_id and built-in presets grouped by skeleton.

Instructions

列出可用的动作:自己文字生成过的动作资产(可用 motion_asset_id 复用),以及按骨骼类型分组的内置预设动作名。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
rig_typeNo只看某种骨骼的预设,默认全部

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It discloses the shape of the response (two result categories, presets bucketed by rig type) and that returned motion_asset_id values are reusable, which is genuinely useful. However, it never states that the call is read-only, whether results are paginated, or whether user assets require auth/project scope.

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?

One compact sentence with the main result categories front-loaded and the parenthetical adding real information rather than filler. Nothing extraneous, though the sentence is dense enough that the filter parameter gets buried.

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 simple, single-optional-parameter listing tool with no output schema, the description explains what comes back and how it is organized, which is the main thing an agent needs. Remaining gaps (pagination, empty-result behavior, ordering) are minor at this complexity.

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 description coverage is 100% and the single rig_type parameter has a documented description plus a full enum, so the schema already does the work. The description's phrase 'grouped by rig type' only loosely gestures at the filter; under the coverage-based baseline this stays at 3.

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?

The description states a specific verb (列出/list) and resource (动作/motions) and even splits the result into two kinds: user-generated text motion assets and built-in presets grouped by rig type. That is far more precise than the name alone. It only misses an explicit contrast with the sibling that consumes these motions (tripo_animate), so it is clear but not sibling-differentiated.

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 parenthetical '可用 motion_asset_id 复用' implies the downstream workflow (fetch an id here, then reuse it), but the description never says when to call this versus tripo_animate or tripo_rig. Usage must be inferred from the mention of asset ids rather than stated outright.

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