Skip to main content
Glama

Animate a PNG locally (no ChatGPT)

animate_image

Animates a local PNG with a chosen looping motion (bounce, idle, sway, nod, squash, or wiggle) and saves a new GIF beside it without altering the source file.

Instructions

Move a local PNG (e.g. a sticker saved with transparent_background=true) with code and save a new looping GIF beside it as _.gif, without overwriting files. No ChatGPT, no Chrome; takes seconds. The character stays unchanged: it only bounces, sways, squashes or breathes. For pose changes such as walking or waving, use generate_sprite. The source PNG is never changed. Returns a numbered preview of every frame.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "image_path": "<image_path>",
      "motion": "<motion>"
    },
    "name": "animate_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoOutput long-edge limit in pixels; enlargement uses the nearest whole multiple of the source pixel grid, so the result may be smaller.
motionYesbounce: jump and land; idle: gentle breathing; sway: rock side to side; nod: dip the head; squash: squash and stretch; wiggle: quick little shake.
backgroundNotransparent
image_pathYesAbsolute path preferred (e.g. a path saved by generate_image); a relative path is resolved from the server's current folder.
include_previewNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (non-read-only, non-destructive), it discloses that files are never overwritten, the source PNG is never modified, the character is not reshaped, and it returns a numbered preview of every frame. It also sets a latency expectation ('takes seconds') and rules out external services.

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?

Front-loaded with the core action and output naming, then the exclusion, then the safety note. The 'No ChatGPT, no Chrome; takes seconds' clause is mildly promotional but still carries usable locality and latency information.

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?

With no output schema, the description covers return shape ('numbered preview of every frame') and the output filename, which is the key thing an agent needs to locate the result. It stops short of stating the actual returned path field or failure behavior for a missing PNG.

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 coverage is 60% and the schema already documents motion enum values, the size minimum/maximum, and image_path resolution. The description adds only the filename templating and the fact that a preview is returned, leaving size, background, and include_preview semantics to the schema.

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: move a local PNG with code and save a looping GIF named <name>_<motion>.gif beside the source. It also explicitly routes pose changes (walking, waving) to generate_sprite, so an agent can separate this from the sibling without inspecting either 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?

Names the alternative (generate_sprite) and the exact condition that selects it ('for pose changes such as walking or waving'). It also gives a prerequisite example (a sticker saved with transparent_background=true) and states the operation is local, fast, and leaves the source untouched.

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