Skip to main content
Glama

create_animation_preview

Capture sampled frames from a Blender animation to generate a preview strip, letting you visually verify motion and timing before rendering.

Instructions

Capture frames for an animation preview strip.

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

Input Schema

NameRequiredDescriptionDefault
stepNo
frame_endNo
frame_startNo

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 supplied, so the description carries the full behavioral burden and delivers almost nothing: it does not say whether this triggers a render (costly), writes files to disk, or is a cheap read. It also omits frame-range defaults, how many frames 'step' produces, and whether existing previews are overwritten.

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?

It is a single front-loaded sentence with no wasted words, which is structurally sound. But the brevity comes at the cost of under-specification rather than genuine economy, since key facts about behavior and parameters are simply absent.

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?

An output schema exists, so return values need not be spelled out. Everything else is missing though: with no annotations, three undocumented parameters, and a sibling set full of overlapping preview/render tools, the definition does not give an agent enough to call this correctly or know what it costs.

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

Parameters3/5

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

Schema description coverage is 0% across three parameters, so the description should compensate, and it does not explain any of them. 'frame_start' and 'frame_end' are largely self-describing from their names, but 'step' (default 5) is ambiguous and its role in sampling frames is never clarified. A 3 reflects that the names carry partial meaning on their own while the description adds nothing.

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?

The verb 'capture' plus the resource 'animation preview strip' gives a rough idea, and the 'animation' qualifier distinguishes it from siblings like capture_scene_preview and capture_material_preview. However, it never says what a 'preview strip' actually is (a rendered image sequence? a contact sheet? files on disk?) or what 'capture' produces, so the purpose stays vague.

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 and no mention of any alternative, even though render_preview, render_animation, and capture_scene_preview sit in the same namespace and clearly overlap. The agent is left to guess whether this previews an existing render or triggers one.

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