Skip to main content
Glama

ai_modeling_motion_presets

Read-only

List available Studio animation preset identifiers by skeleton type and category from a dated local catalogue, so you can choose compatible motions without logging in.

Instructions

List Studio preset animation identifiers by skeleton and category. Uses a dated local catalogue; no login required.

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": "ai_modeling_motion_presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNo
rig_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds two things the annotations do not: the data is a 'dated local catalogue' (results may be stale/static) and 'no login required' (no auth gating). It does not explain pagination or result volume.

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?

Two short sentences with the primary action front-loaded and the operational caveat second. No redundant wording; 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 simple, zero-required-parameter read tool with no output schema, the description covers what it returns ('identifiers'), the filtering axes, and the data source freshness. The main remaining gap is the default behavior when no filters are supplied.

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 0%, but both parameters carry full enums in the schema, so allowed values are fully discoverable. The description contributes the useful mapping that 'skeleton' corresponds to the rig_type parameter and that filtering is by category, but it does not state that both filters are optional or what omitting them returns.

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 uses a specific verb and resource: 'List Studio preset animation identifiers', scoped by skeleton and category. That distinguishes it from the motion_* siblings, which deal with motions rather than preset catalogues, though no sibling is named explicitly.

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?

Usage context is only implied: 'Uses a dated local catalogue; no login required' signals an offline, unauthenticated lookup, which is useful for deciding when this is viable. However, there is no explicit statement of when to prefer presets over the motion_list/motion_get siblings, nor of any precondition or exclusion.

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