Skip to main content
Glama

animate

Create an APNG or GIF from ordered image paths to show a short sequence of states. Preview in a temp draft first, then save to the output folder.

Instructions

Animation from image paths, one frame per image: APNG (full color, default) or GIF (plays everywhere: Slack, mail, Jira). Use it to show a short sequence of states; for steps the user should read, make_guide is clearer. Draft by default (temp folder): check the preview, then call again with draft=false to save to the output folder. The preview shows the first frame. Writes one file; the inputs are not changed. Returns the path, frame count, format, size and a preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loopNoRepeat count; 0 = forever.
nameNoBase file name in the output folder, no extension. Empty = tool default.
draftNotrue (default): write to a temp folder so you can check the preview first. false: save to the output folder (~/Pictures/AInotate unless configured) and the backup folder.
formatNo"apng" (full color, default) or "gif".apng
framesYesImage paths, one per frame, in order. Frames are scaled to the first one.
duration_msNoTime per frame in ms (default 1500).
crossfade_msNoLength of a blended transition between frames in ms; 0 = cut.
durations_msNoOld name of duration_ms; used only when duration_ms is not given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.1.1
    • addedInput schema / properties / crossfade_ms / description
      Added value: +"Length of a blended transition between frames in ms; 0 = cut."
    • addedInput schema / properties / draft / description
      Added value: +"true (default): write to a temp folder so you can check the preview first. false: save to the output folder (~/Pictures/AInotate unless configured) and the backup folder."
    • addedInput schema / properties / duration_ms / description
      Added value: +"Time per frame in ms (default 1500)."
    • addedInput schema / properties / durations_ms / description
      Added value: +"Old name of duration_ms; used only when duration_ms is not given."
    • addedInput schema / properties / format / description
      Added value: +"\"apng\" (full color, default) or \"gif\"."
    • addedInput schema / properties / frames / description
      Added value: +"Image paths, one per frame, in order. Frames are scaled to the first one."
    • addedInput schema / properties / loop / description
      Added value: +"Repeat count; 0 = forever."
    • addedInput schema / properties / name / description
      Added value: +"Base file name in the output folder, no extension. Empty = tool default."
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world behavior, and the description adds substantial context beyond that: default draft writes to a temp folder, draft=false writes to the output folder plus a backup, only one file is written, inputs are not mutated, and the preview shows the first frame. This is exactly the kind of behavioral detail an agent needs before invoking a file-writing tool.

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?

Dense but front-loaded: purpose and format first, then sibling routing, then the draft workflow, then return values. Every sentence carries distinct information with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by enumerating the return payload (path, frame count, format, size, preview). Combined with the workflow and side-effect disclosure, nothing an agent needs to call this correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema for format ('APNG full color default' vs 'GIF plays everywhere: Slack, mail, Jira') and the draft flag's side effects, including the backup folder. Loop, name, and duration fields are left to the schema, which already documents them.

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?

States a specific verb and resource (animation from image paths, one frame per image), names the two output formats and their defaults, and explicitly distinguishes itself from the sibling make_guide. An agent can identify this tool and its output without opening the schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use ('show a short sequence of states') and when-not ('for steps the user should read, make_guide is clearer'), plus the recommended two-step workflow: draft first, inspect the preview, then re-call with draft=false. Alternatives and conditions are fully spelled out.

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