Skip to main content
Glama

animate

Generate videos or GIF animations from scientific simulation data using time series playback or orbital camera rotation. Adjust speed, resolution, and add text overlays.

Instructions

Create an animation from time series data or camera orbit.

Time mapping (timesteps mode): speed_factor=1.0: real-time (physics 1s = video 1s) speed_factor=5.0: 5x fast-forward speed_factor=0.2: 5x slow-motion (physics 1s = video 5s)

For VTK file series (e.g., PartFluid_0000.vtk through PartFluid_0100.vtk), use 'files' with an explicit list or 'file_pattern' with a glob pattern.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesPath to simulation file (or first file in series)
field_nameYesField to visualize
modeNo"timesteps" for time series, "orbit" for camera rotationtimesteps
colormapNoColor map presetCool to Warm
cameraNoCamera preset (used for initial view in orbit mode)isometric
fpsNoFrames per second (15-60)
time_rangeNo[start, end] physics time range, None for all
speed_factorNoPlayback speed multiplier (1.0=real-time)
orbit_durationNoOrbit video length in seconds (orbit mode only)
widthNoFrame width
heightNoFrame height
filesNoExplicit list of file paths for VTK time series
file_patternNoGlob pattern for file series (e.g., "/data/PartFluid_*.vtk")
output_formatNoOutput format — "frames" (PNG only), "mp4", "webm", or "gif"frames
video_qualityNoVideo CRF quality (lower=better, 18-28 typical, default 23)
text_overlayNoText to overlay on video frames (e.g., case name)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, the description carries full burden. It explains speed_factor mapping (real-time, fast-forward, slow-motion), file pattern usage, and output formats. Side effects like file creation are implied but not detailed.

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?

The description is moderately long but well-organized into paragraphs for different modes and file handling. It could be more terse, but no sentence is wasted. The key details are front-loaded.

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?

Given 16 parameters with 100% schema coverage and an output schema, the description adds essential context for both modes and VTK series handling. It is sufficient for an agent to use the tool correctly.

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

Parameters4/5

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

Schema description coverage is 100%, baseline 3. The description adds meaning beyond schemas by explaining speed_factor physics-to-video mapping and the difference between files and file_pattern for VTK series.

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

Purpose5/5

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

The description clearly states the tool creates animations from time series data or camera orbit, with two named modes (timesteps/orbit). This verb+resource combination is specific and distinguishes from siblings like render and split_animate.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use timesteps vs orbit modes and provides guidance for VTK file series (use files or file_pattern). However, it does not explicitly mention when not to use this tool versus alternatives like cinematic_render or batch_render.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kimimgo/viznoir'

If you have feedback or need assistance with the MCP directory API, please join our Discord server