Skip to main content
Glama

ai_modeling_motion_list

Read-only

Lists generated motion assets so agents can review, select, and manage available animations for editing or project use.

Instructions

List your generated motion assets.

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_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered and the bar is lower. The description adds the scoping nuance that these are 'your generated' assets as opposed to shared/preset content, but says nothing about pagination, result caps, or ordering, which matter for a list operation with no output schema.

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 front-loaded sentence with no hedging or redundancy. It is efficient, though the terseness edges toward under-specification rather than optimal conciseness for a list tool.

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

Completeness2/5

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

For a list tool with no output schema and no parameter documentation to fall back on, the definition leaves out result shape, ordering, and pagination behavior entirely. With ten-plus 'list'-style siblings in the namespace, the absence of any routing or scope detail makes this inadequate for confident selection.

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?

The tool takes zero parameters, so per the baseline this dimension scores 4. There is nothing in the schema for the description to elaborate on, and the empty object schema matches the no-argument nature of the call.

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

Purpose3/5

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

The verb 'List' plus the resource 'generated motion assets' is specific enough to convey the operation, and 'generated' hints at user-produced assets rather than presets. However, it offers no differentiation from close siblings such as ai_modeling_motion_recent, ai_modeling_assets_list, or ai_modeling_motion_presets, so an agent cannot tell which listing tool applies without opening schemas.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no mention of alternatives. The description gives no signal about whether this lists all assets ever generated, only the latest, or how it relates to the recent/presets/active siblings.

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