Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

ambient_motion

Animate a still Aseprite scene into a looping effect by adding wind, water shimmer, glint sweeps, or particles across generated frames.

Instructions

Bring a still scene to life as a seamless loop. layer (the active layer by default) is animated from from_frame over frames frames of duration_ms: wind (pixels, try 1) sends gusts rolling left to right, one per wavelength pixels; shimmer (pixels) wobbles rows like water; glint (0-1) sweeps light across the bright pixels once a loop. particles adds a layer of motes, snow, rain, or embers. Animate each part on its own layer (see split_into_layers) so armour can glint while grass blows. Frames are added as needed, copying the others, and tagged tag. Check with check_loop. One undo step. Headless: pass file.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ambient_motion"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoloop
fileNo
seedNo
windNo
glintNo
layerNo
framesNo
shimmerNo
particlesNo
from_frameNo
wavelengthNo
duration_msNo
glint_colorNo#ffecbe
particle_countNo
particle_colorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only carry a title, so the description bears the load and does disclose non-obvious behavior: frames are added as needed by copying existing ones, they are tagged with tag, the operation costs exactly one undo step, and headless calls require file. It does not describe what happens to the active layer selection or how errors surface, leaving some behavioral surface unreported.

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 purpose is front-loaded in the first sentence, effects are then introduced in a compact backtick-annotated sequence that maps directly to parameter names, and workflow notes are clustered at the end. Given 15 parameters, nothing reads as filler.

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

Completeness3/5

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

For a 15-parameter tool with 0% schema description coverage and no output schema, the description covers most of the animation knobs but silently omits seed, glint_color, particle_count, and particle_colors, leaving an agent to guess their effect. The workflow and undo/headless notes help, but the parameter documentation gap is material at this complexity.

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 0%, so the description must supply meaning and it largely does: wind and shimmer are in pixels with a suggested value of 1, glint is 0-1, wavelength is in pixels, particles accepts motes/snow/rain/embers, and from_frame/frames/duration_ms are tied together. Four parameters (seed, glint_color, particle_count, particle_colors) get no explanation at all, which keeps it below a top score.

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 opens with a specific verb and outcome ('Bring a still scene to life as a seamless loop') and then enumerates the exact effects applied (wind, shimmer, glint, particles), so an agent knows precisely what the tool produces. It also names the complementary tools (split_into_layers, check_loop) that shape how the result is composed.

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 concrete workflow guidance: animate each part on its own layer via split_into_layers so armour can glint while grass blows, verify the result with check_loop, and pass file when running headless. It stops short of stating when NOT to use this tool or contrasting it with sibling animation tools, so it is clear context without explicit exclusions.

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