Skip to main content
Glama

animate_location

Keyframe an object's location at a specified frame to create motion animation.

Instructions

Keyframe object location.

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": {
      "name": "<name>",
      "location": "<location>",
      "frame": "<frame>"
    },
    "name": "animate_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
frameYes
locationYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not explain whether keyframes are inserted or replace existing ones, what interpolation is used, whether the object must already exist, what frame range is valid, or what side effects occur.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only four words and is front-loaded, but it is under-specified rather than appropriately concise. Brevity here removes necessary detail instead of eliminating waste.

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 three-required-parameter animation mutation tool with no annotations and no schema descriptions, the description is not complete enough for reliable invocation. The output schema reduces the need to explain return values, but key behavioral and parameter details are still missing.

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 must compensate for all three parameters. It only hints that 'location' is spatial; it does not explain that 'name' identifies the object or that 'frame' is a timeline position, leaving most parameter meaning undocumented.

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 ('Keyframe') and resource ('object location'), making the tool's purpose clear. It implicitly distinguishes itself from siblings like animate_rotation and animate_scale by targeting location, though it does not name those alternatives explicitly.

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 guidance on when to use this tool versus animate_rotation, animate_scale, or other animation tools. The only usage signal is the implied act of keyframing an object's location, with no prerequisites or exclusions mentioned.

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