Skip to main content
Glama

animate_rotation

Keyframe an object's rotation at a specific frame to build rotation animations in Blender. Specify the object name, rotation values, and target frame.

Instructions

Keyframe object rotation.

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>",
      "rotation": "<rotation>",
      "frame": "<frame>"
    },
    "name": "animate_rotation"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
frameYes
rotationYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/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 behavioral burden and delivers almost nothing. It does not state whether existing keyframes are overwritten, what interpolation is applied, whether rotation is Euler or quaternion (or degrees vs radians), or whether the operation needs the object to exist/be selected. With an output schema present the return shape need not be explained, but the mutation semantics remain opaque.

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?

Four words are technically concise but represent under-specification rather than economy; there is no structure, no front-loaded context, and nothing for the agent to act on beyond the tool name. Brevity here costs rather than saves effort.

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?

This is a mutation tool with three fully undocumented required parameters and no annotations, so the definition falls well short of what an agent needs to invoke it correctly. The existing output schema covers return-value expectations, but the input contract and side effects are missing.

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

Parameters1/5

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

All three required parameters (name, rotation, frame) have 0% schema description coverage and the description adds no meaning to any of them. Critical ambiguities — whether 'name' is an object name or a data path, whether 'rotation' is a 3-value Euler array and in what units, and whether 'frame' is zero- or one-based — are left entirely unresolved.

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?

'Keyframe object rotation' supplies a specific verb (keyframe) and resource (rotation), which distinguishes it from siblings animate_location and animate_scale by resource alone. However, it gives no scope detail — no statement of what object is targeted, what property is animated, or what 'keyframe' means operationally.

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 prerequisites (e.g., object must be selected/active), and no mention of alternatives or when not to use this tool. The only hint at differentiation is the word 'rotation' versus sibling names the agent may not see side by side.

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