Skip to main content
Glama

ai_modeling_motion

Generate an animation from a text motion description using your Studio account and a stable request ID; reuse safely returns the original job instead of creating a duplicate.

Instructions

generate an animation from a motion description. Uses your Studio account and a stable request_id. Reuse returns the original job; changed input conflicts; outcome_unknown must never be blindly retried.

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": {
      "request_id": "<request_id>",
      "max_estimated_credits": "<max_estimated_credits>",
      "parameters": "<parameters>"
    },
    "name": "ai_modeling_motion"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYes
request_idYes
max_estimated_creditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already flag openWorldHint and non-read-only, so the safety bar is partly met. The description adds valuable context those annotations cannot express: it bills against the Studio account and it defines idempotency and conflict semantics on request_id, which is exactly the failure mode an agent needs. Missing is any statement about credit consumption or what a successful call returns.

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?

Three dense, front-loaded sentences with no filler, and the idempotency contract comes straight after the purpose. The telegraphic fragments ('changed input conflicts') are slightly compressed but still parseable, so the brevity does not cost clarity.

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 generation tool with a nested input object, no output schema, and zero schema descriptions, the description covers the critical operational semantics (identity, idempotency, retry policy) well. It is still incomplete on the request body and on what comes back from a successful generation, which an agent needs to chain calls.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for three required parameters with a nested segments array (prompt, duration_seconds, waypoints). It mentions request_id only in the context of retry behavior and never explains segments, waypoints, or max_estimated_credits, leaving the caller to infer the whole payload shape from raw JSON Schema.

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: 'generate an animation from a motion description'. That is clearly distinct from the read-style siblings (motion_get, motion_list, motion_task), though it doesn't explicitly point to a sibling alternative. It is clear but leaves sibling differentiation to inference.

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?

Provides real usage rules for retries: reuse of a request_id returns the original job, changed input conflicts, and outcome_unknown must not be blindly retried. However, it never says when to call this versus polling via motion_task / motion_get, or how credits are consumed, so the when-to-use guidance is implied rather than complete.

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