Skip to main content
Glama

inspect_animation

Retrieve and examine animation data in Blender scenes to verify keyframes, timing, and object motion before rendering or further edits.

Instructions

Inspect animation data.

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": "inspect_animation"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden yet says nothing about whether this is a safe read operation, what happens when no animation exists, or whether it needs an active object/action in context. Only the presence of an output schema spares it from a lower score.

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

Conciseness3/5

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

The single sentence is tight and front-loaded, but it is under-specified rather than concise — brevity here comes at the cost of any actionable content.

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?

The output schema covers return values, but the tool still leaves the meaning of its only parameter and its relationship to the near-identical sibling get_animation_info unexplained. For a read tool with a nested inspection domain (actions, keyframes, F-curves), this is insufficient to call correctly.

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% for the single optional 'name' parameter, and the description does not clarify whether 'name' refers to an object, an action, a bone, or an NLA track. Because the parameter is optional, an agent also cannot infer from the text what the default targeting behavior is.

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

Purpose2/5

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

The description restates the tool name almost verbatim: 'Inspect animation data' adds no specific resource scope, verb nuance, or distinguishing detail. It is indistinguishable from the sibling get_animation_info by this text alone, so an agent cannot tell what 'inspect' covers that 'get info' does not.

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

Usage Guidelines1/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 exclusion, and no mention of the sibling get_animation_info or create_animation_preview that an agent would need to route between. Nothing indicates whether this requires an open scene, a selected object, or an existing action.

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