Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

export_animation

Exports Aseprite animations as looping GIF or animated PNG files at a specified path. Preserves per-frame durations and scales pixels sharply for game assets.

Instructions

Write the animation (or one tag) as a looping .gif or animated .png at path, scaled up scale times with sharp pixels (4 turns a 384x128 banner into 1536x512). Each frame keeps its own duration. An animated PNG keeps transparency; a GIF is laid on background (#rrggbb, black by default), as are both when it's given. Written from Python, so the live editor shows no security prompt. Headless: pass file.

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": {
      "path": "<path>"
    },
    "name": "export_animation"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
fileNo
pathYes
scaleNo
backgroundNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=false, title only), the description discloses substantial behavior: each frame retains its own duration, looping output, animated PNG preserves transparency, GIF is composited on `background` (default black #rrggbb) as is PNG when a background is given, and sharp-pixel scaling with a worked example (4 turns 384x128 into 1536x512). It also explains the execution environment difference (Python write with no editor security prompt vs. headless needing `file`), which an agent cannot get from the schema or annotations.

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?

One dense paragraph, front-loaded with the core action and output format, then scaling, then transparency/background rules, then the headless caveat — a sensible ordering with little filler. The doubled-backtick markup and abrupt final sentence ('Headless: pass `file`.') slightly hurt readability.

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, no parameter descriptions, and only a destructiveHint annotation, the description does the heavy lifting: formats, loop behavior, scaling, transparency, background defaults, and the headless requirement. It is complete enough to call correctly, though it never says whether an existing file at `path` is overwritten or what is returned on success.

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 0% across five parameters, so the description carries the full burden and mostly succeeds: it defines `tag` (export one tag instead of all), `path` (destination), `scale` (integer upscale multiplier with sharp pixels, example value 4), `background` (#rrggbb, black default, with format-specific transparency rules). It covers all five params but leaves `file` vague — it is only described as 'Headless: pass file' without saying what the value should be.

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

Purpose4/5

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

The description pairs a specific verb with a specific resource and output formats: write the animation (or one tag) as a looping .gif or animated .png at path. That implicitly separates it from the static-image exporters (export_sprite, export_spritesheet), but it never names an alternative explicitly, so sibling differentiation is inferred rather than stated.

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?

It gives real conditional context: use `tag` to export a single tag rather than the whole animation, and pass `file` when running headless since the live editor path shows no security prompt. There is no explicit when-not guidance or comparison to the other export_* tools, so it stops short of full routing guidance.

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