Skip to main content
Glama

ai_modeling_motion_recent

Read-only

Lists recently used retarget motions for your Studio account so you can quickly find and reuse prior animations.

Instructions

List recently used retarget motions for your Studio account.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds essentially nothing beyond the name: it does not define what 'recently' means (time window or count), nor the ordering, page size, or whether the result is empty for new accounts.

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 sentence with no filler and the key scope ('recently used') front-loaded. It earns its place but is thin enough that brevity shades into under-specification rather than optimal density.

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 zero-parameter read-only list tool with no output schema and full annotation coverage, this is minimally sufficient to select and call it. The missing piece is defining the recency window and result ordering, which the agent cannot get from any structured field.

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 the baseline of 4 applies. No schema semantics need explaining and the description introduces no misleading parameter expectations.

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: 'List recently used retarget motions' scoped to 'your Studio account.' An agent can tell this returns a recency-filtered motion collection, distinct from a general listing. It stops short of naming how it differs from siblings such as ai_modeling_motion_list or ai_modeling_motion_active.

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?

The word 'recently' implies a use case, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative such as the full motion list. The agent must infer the selection criteria from the adjective alone.

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