Skip to main content
Glama

animate

Create animations from time series simulation data or camera orbits with configurable speed, timing, and output formats including MP4, WebM, and GIF.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changedv0.8.0
    • addedInput schema / properties / camera / description
      Added value: +"Camera preset (used for initial view in orbit mode)"
    • addedInput schema / properties / colormap / description
      Added value: +"Color map preset"
    • addedInput schema / properties / field_name / description
      Added value: +"Field to visualize"
    • addedInput schema / properties / file_path / description
      Added value: +"Path to simulation file (or first file in series)"
    • addedInput schema / properties / file_pattern / description
      Added value: +"Glob pattern for file series (e.g., \"/data/PartFluid_*.vtk\")"
    • addedInput schema / properties / files / description
      Added value: +"Explicit list of file paths for VTK time series"
    • addedInput schema / properties / fps / description
      Added value: +"Frames per second (15-60)"
    • addedInput schema / properties / height / description
      Added value: +"Frame height"
    • addedInput schema / properties / mode / description
      Added value: +"\"timesteps\" for time series, \"orbit\" for camera rotation"
    • addedInput schema / properties / orbit_duration / description
      Added value: +"Orbit video length in seconds (orbit mode only)"
    • addedInput schema / properties / output_format / description
      Added value: +"Output format — \"frames\" (PNG only), \"mp4\", \"webm\", or \"gif\""
    • addedInput schema / properties / speed_factor / description
      Added value: +"Playback speed multiplier (1.0=real-time)"
    • addedInput schema / properties / text_overlay / description
      Added value: +"Text to overlay on video frames (e.g., case name)"
    • addedInput schema / properties / time_range / description
      Added value: +"[start, end] physics time range, None for all"
    • addedInput schema / properties / video_quality / description
      Added value: +"Video CRF quality (lower=better, 18-28 typical, default 23)"
    • addedInput schema / properties / width / description
      Added value: +"Frame width"
  2. First observedv0.7.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations provided, the description must disclose behavioral traits. It explains speed_factor mapping and output formats, but does not mention output file locations, overwrite behavior, or side effects. This is adequate but leaves some gaps.

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

Conciseness5/5

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

The description is concise (about 10 lines) and front-loaded with the core purpose. Every sentence provides useful information without redundancy or verbosity.

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 the complexity (16 parameters, output schema exists), the description covers the main modes and key behaviors. It does not detail output file naming or save location, but the output schema likely covers return values. Overall, it is fairly complete.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds extra semantic value by explaining speed_factor mapping (real-time vs fast-forward vs slow-motion) and VTK file pattern usage, which goes beyond the schema descriptions.

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 identifies the tool's purpose: creating animations from time series data or camera orbits. It specifies two distinct modes (timesteps and orbit), which differentiates it from siblings like render or batch_render.

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 provides guidance on when to use each mode and explains speed_factor scaling. It also mentions VTK file series usage. However, it lacks explicit comparisons to alternatives like split_animate, and could more clearly state when not to use this tool.

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