aseprite-ai-artist
This server lets an AI agent paint pixel art and animation directly inside a live or headless Aseprite session, verifying its work by looking at the canvas after every change.
Connect & inspect —
preflightchecks Aseprite is attached and picks live vs. headless mode;sprite_infodumps full document state (dimensions, palette, layers, frames, tags, slices, selection).Manage documents —
sprite_manageopens, creates, focuses, resizes, saves, closes sprites, and creates/updates/deletes slices (9-patch centers, pivots).Look at the art —
lookreturns previews, exact ASCII pixel grids, filmstrips, onion skins, frame diffs, and reference comparisons;read_pixelsgives structured colour/index data for computation.Draw —
drawapplies batched, single-undo operations: pixels, lines, shapes, fills, dither, gradients, blits, bitmap text, and whole pictures typed as character grids;paletteLockkeeps colours palette-legal.Select & transform —
select(rect, ellipse, colour, grow/shrink, invert) scopes edits;transformmoves, flips, rotates 90°, scales, outlines, and crops a cel.Layers, frames, cels, tags —
layer,frame,cel, andtagcreate/arrange rigs, key poses, durations, cel linking, tweens and oscillation, and named animation cycles for engines.Colour work —
palettegets/sets/loads presets, generates hue-shifted ramps, analyzes, and extracts palettes;recolorshades, snaps, replaces, hue-shifts, and desaturates by intent.Quality control —
validatelints for off-palette colours, strays, outline breaks, banding, bad anti-aliasing, empty layers, untagged frames, timing drift, and volume drift, plus custom animation contracts.References —
referenceimports concept sheets or storyboards as locked layers, splits panels across frames, and samples dominant colours.Export —
exportwrites PNGs, GIFs, packed spritesheets with JSON atlases, numbered frame sequences, and.asepritecopies.Tilesets —
tilesetlists/creates tilemap layers, stamps tiles, packs hand-painted mockups into deduplicated tilesets, and exports Tiled/Godot/JSON with optional blob47 autotiling.
Allows AI agents to draw and edit pixel art directly in an open Aseprite document, including creating and modifying sprites, layers, frames, tags, and cels, with tools for pixel-level drawing, selection, recoloring, and validation.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@aseprite-ai-artistDraw me a 32x32 knight with a 4-frame idle animation."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Aseprite AI Artist
Your coding agent, painting in the Aseprite window you already have open.
Not a generated PNG. Not a file changed behind your back. The document on your screen, one pixel at a time — and every step is one Ctrl+Z.
☔ 500×400 · 384 frames at 24 fps · 16 s · 24 layers — drawn by Claude Opus 5.5 through this server.
Install · How it draws · Skills · Gallery
✨ What it feels like
"Draw me a 32×32 knight in the PICO-8 palette, then give him a 4-frame idle."
You type that, and watch it happen in Aseprite: a palette, a silhouette, shading, layers, a breathing idle, a tagged cycle. The agent looks at its own work after every step, and at the end tells you what it compromised on.
You stay in charge. Don't like the helmet? Ctrl+Z, or just say so.
Works with Claude Code, omp, OpenCode, Codex CLI, Gemini CLI, Cursor, VS Code and Windsurf. Best results so far: Claude Opus 5.5.
Related MCP server: Aseprite MCP Tools
🚀 Install
You need Aseprite 1.3+ and Node 22.6+ (macOS, Linux or Windows).
1. The Aseprite extension — then quit and reopen Aseprite:
npx @pebbly/aseprite-ai-artist install-extension2. Your agent:
/plugin marketplace add with-pebbly/aseprite-ai-artist
/plugin install aseprite@aseprite-ai-artistomp plugin marketplace add with-pebbly/aseprite-ai-artist
omp plugin install aseprite@aseprite-ai-artistnpx @pebbly/aseprite-ai-artist install opencode
opencode plugin add github:with-pebbly/aseprite-ai-artist#main::path:opencodenpx @pebbly/aseprite-ai-artist install codex # or gemini, cursor, --allYour config is backed up first; --dry-run shows the change.
3. Check it — restart your agent, then:
npx @pebbly/aseprite-ai-artist doctorAll ticks means you're ready. Updating? Run step 1 again. Odd setups (Steam, custom folders, Windows paths) are in docs/INSTALL.md.
For CI or a batch of assets, the server can run Aseprite itself with no window:
npx @pebbly/aseprite-ai-artist serve --headless --aseprite /path/to/asepriteNothing is on disk until the agent saves, and it never touches a file your editor has open. It is never a fallback: if your window isn't attached, the agent asks instead of quietly switching.
🎨 How it draws
Ask /aseprite:studio for anything and it runs the whole job:
Stage | What happens | |
1 | Connect | Checks Aseprite is attached and reads what's open. If it isn't, it stops — it never edits files behind your back. |
2 | Brief | Only for open-ended requests: size, palette, view, light — one message, one answer. |
3 | Concept | For anything new: writes the design down and gives you a prompt for an image model. Send back a concept sheet, or say "continue without". |
4 | Draw | Silhouette first, written as a text grid (below), then shading. |
5 | Animate | Splits limbs onto layers, plans key poses and timing, draws each frame, tags the cycles. |
6 | Review | A separate critic who didn't draw it judges the result cold — what does it look like to someone never told? Blockers get fixed one at a time; a fix is kept only if the critic, shown both versions blind, prefers it. |
7 | Export | Spritesheet + atlas, GIF or PNGs for your engine. |
After every step that changed pixels, it looks at the result before moving on.
🔤 The grid loop
New in 0.5.0. The agent doesn't draw with circles and rectangles — it types the frame out, one character per pixel, and draws that text in one call. To fix something, it reads the canvas back in the same format and changes only the characters that are wrong.
It sees the whole shape while writing it, so silhouettes stay even, limbs keep their length between frames, and an edit never spills into its neighbours. Animation is the same trick: copy the last frame's rows, move the arm, draw.
Since 0.6.0 every character stands for one palette entry, the same on every read, so a big canvas can be read and edited in pieces without the letters changing meaning between them. A grid can be as large as the canvas.
Early signal, not a measurement: with the same model and prompts, the mage benchmark went 3 → 4/10 and the road 1 → 3/10; the tree stayed at 2 (compare them).
📚 The pixel-art knowledge base
The agent doesn't improvise a hand at 16 px or a horse's walk — it looks them up.
62 rules · ~400 pixel templates · 2006 palettes — browse them at pixeli.pebbly.space/knowledge 👀
🧍 Craft | 🌍 World |
|
|
|
|
|
|
|
|
|
|
Every rule gives size budgets, a procedure, common mistakes and grid templates
the agent pastes straight onto the canvas. Any MCP client reads them as
rules:// resources from rules/.
🎨 Palettes: the console classics plus Lospec's 2000 most-downloaded, each
credited — preset: "endesga-32", or just a word of the name.
👀 Review by fresh eyes
New in 0.8.0. The agent that drew a sprite is the worst judge of it — it
knows what it meant, so it sees it. studio hands the result to
pixel-critic, which first writes a cold read (what the picture shows to
someone who was never told), then a scored critique. A draft ships at 7/10
with nothing blocking; below that the agent fixes the one thing named,
snapshotting first. Each fix goes back to the critic as a blind A/B — old and
new under neutral names — and stays only if it wins, so a round can't quietly
make good art worse.
It costs time (roughly one more critique per round) and its effect on quality is not yet measured — the thirteen experiment runs behind it are in the gallery, next to the benchmark rows.
🧰 Skills
studio picks these for you. Call one directly when you know the step you want
— as /aseprite:<name> in Claude Code and omp, or just ask elsewhere.
Skill | For | Try |
🎬 | anything — it plans and runs the rest |
|
📝 | a vague idea |
|
🖼️ | a design or storyboard before drawing |
|
📄 | a fresh document set up right |
|
🎨 | colour: a retro look, ramps, cleanup |
|
✏️ | making the thing, text included |
|
🌗 | flat art that needs light |
|
🦴 | splitting a character for animation |
|
🏃 | walk, idle, attack cycles |
|
🧱 | terrain and autotiles |
|
🔍 | an honest critique |
|
🩹 | changing art without wrecking it |
|
📦 | files for your engine |
|
🗂️ | sharing it in the gallery |
|
In Claude Code and omp, four specialists take stages off the main agent: palette-smith, rig-builder, animation-director and the read-only pixel-critic.
🏆 Which model?
Live from the benchmark: every model draws the same fixed prompts and is scored against written criteria. Your model is not on it? Send us a sprite!
🗂️ Gallery and benchmark
Everything drawn with the plugin — with its prompts, models and .aseprite
source — is at pixeli.pebbly.space. The
benchmark puts every model and plugin version through the same three fixed
prompts and scores them against written criteria, and the
knowledge base shows the rulebook
the agents draw by.
Made something? Ask your agent for /aseprite:submit — it packages the files
and opens the pull request.
🔧 Under the hood
your agent ──MCP──▶ server ──▶ bridge ──▶ Aseprite extension18 tools, grouped by noun (
draw,look,layer,frame,export…) instead of ninety — every tool costs context on every turn. Reference.A knowledge base in
rules/— 62 files from line craft to walk cycles, with pixel templates — served over MCP, so every client gets the same craft knowledge.Safe by default. Every action is one undo step. With Aseprite detached, tools refuse instead of editing files on disk. Everything binds to
127.0.0.1. Details · security.
🛠️ Development
pnpm install && pnpm run build
pnpm test # TypeScript
pnpm run test:extension # the Lua handlers, inside a real Aseprite
pnpm gallery:check # gallery and benchmark data
pnpm web:dev # the site, locallyRead AGENTS.md before changing anything — it lists the rules that aren't negotiable and the Lua gotchas that already cost someone a day.
📜 Licence
MIT — see LICENSE. Aseprite is a trademark of Igara Studio S.A.; this project isn't affiliated with them.
Available Tools
18 toolscelCelsADestructive
Manage cels — one layer's image on one frame. Ops: 'list', 'create', 'clear', 'delete', 'move', 'copy', 'link', 'unlink', 'set' (position/opacity), 'tween', 'oscillate'. 'move' is how you shift a whole limb between frames without redrawing it; 'link' shares one image across frames so a static part of a cycle stays in sync. 'tween' interpolates position or opacity between two frames with an easing curve; 'oscillate' adds a sinusoidal position offset over a frame range — both fill in any missing in-between cels from the start cel, in one transaction.
| Name | Required | Description | Default |
|---|---|---|---|
| x | No | Cel origin, for 'set' and 'move'. | |
| y | No | ||
| dx | No | Relative move. | |
| dy | No | ||
| op | Yes | ||
| to | No | For 'tween': end value — {x,y} for property 'position', 0-255 for 'opacity'. | |
| frame | No | 1-based frame number. Omit to use the active frame. | |
| layer | No | Layer name. Omit to use the active layer. | |
| phase | No | For 'oscillate': 0-1 fraction of one period. | |
| easing | No | For 'tween'. | linear |
| frames | No | For 'link' across a range. | |
| period | No | For 'oscillate', in frames. Default: the whole fromFrame..toFrame span. | |
| sprite | No | Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused. | |
| opacity | No | ||
| toFrame | No | ||
| toLayer | No | ||
| property | No | For 'tween'. | |
| fromFrame | No | For 'tween'/'oscillate': the start frame. | |
| amplitudeX | No | For 'oscillate'. | |
| amplitudeY | No | For 'oscillate'. |
Output Schema
| Name | Required | Description |
|---|---|---|
| cels | No | |
| frames | No | Only present for 'tween' and 'oscillate': one entry per frame touched, ascending. |
| sprite | Yes | |
| applied | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: tween/oscillate operate 'in one transaction' and 'fill in any missing in-between cels from the start cel,' disclosing atomicity and side effects. It stops short of stating reversibility or permission needs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with purpose followed by the op list, then targeted explanations of the less obvious operations. Dense but nearly every sentence carries information an agent needs to disambiguate ops. Slightly long, though not padded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 20-parameter, 11-operation tool with an output schema present, return values need not be explained. The description covers the op semantics and transaction behavior well, but leaves a few parameter interactions (sprite selection, toLayer/toFrame pairing) to the schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 70%, so the schema does much of the work, but the description adds real semantic value by mapping operations to intent (move vs link vs tween vs oscillate) and clarifying the opacity/position distinction for tween. It does not document every parameter (e.g. sprite, toLayer, frames) but complements the schema well.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource and defines the concept precisely: 'Manage cels — one layer's image on one frame.' It then enumerates all 11 supported operations, so an agent immediately knows the tool's exact scope. It is clearly distinguishable from siblings like layer or frame.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explains what several operations mean and implicitly when to prefer them: 'move' for shifting a limb without redrawing, 'link' for sharing an image across frames, 'tween'/'oscillate' for procedural in-betweens. It gives clear operational context but never explicitly routes the agent away from alternative sibling tools (layer, frame).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
drawDrawA
Apply a batch of drawing operations to one cel, as a single undoable action. Ops: pixels, line, polyline, rect, ellipse, fill, replace, dither, gradient, clear, blit, text, grid. Batch aggressively — a whole sprite in one call is normal and correct, and it means the user can undo your work with one Ctrl+Z. Set paletteLock (default true) to snap every colour to the sprite's palette by perceptual distance before anything is written, so you cannot silently widen a curated palette. Ops run in array order, so paint fills before outlines and outlines before highlights. 'text' is laid out here from a bitmap font and expanded to plain pixels before it reaches Aseprite — pass measureOnly: true with only 'text' ops to get each one's ink bounds without touching the sprite, e.g. to centre a label first. 'grid' paints a picture written as text — one character per pixel, a legend mapping characters to colours, the same shape look op="ascii" returns — so you can see the whole silhouette while you write it instead of composing it from shapes. It is the easiest way to draw a small sprite or a whole animation frame, and to edit one: read a region with look op="ascii" layer=… rulers=false, change the rows, and send them back as a grid at the region's x/y.
| Name | Required | Description | Default |
|---|---|---|---|
| ops | Yes | Applied in order, in one transaction. | |
| frame | No | 1-based frame number. Omit to use the active frame. | |
| label | No | Name shown in Aseprite's undo history. Describe the intent, e.g. 'shade helmet'. | |
| layer | No | Layer name. Omit to use the active layer. | |
| sprite | No | Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused. | |
| createCel | No | Create the cel if the target layer/frame has none. | |
| measureOnly | No | Every op must be 'text'. Returns each one's ink bounds without calling Aseprite at all — use to size a panel or centre a label before actually drawing it. | |
| paletteLock | No | Snap every colour to the nearest palette entry (CIELAB ΔE). Set false only when the user asked to introduce new colours. | |
| selectionOnly | No | Clip every op to the current selection. |
Output Schema
| Name | Required | Description |
|---|---|---|
| frame | No | |
| layer | No | |
| bounds | No | Bounding box actually touched. |
| sprite | No | |
| opsApplied | No | |
| textBounds | No | Only present when `measureOnly` was set. |
| measureOnly | No | |
| colorsSnapped | No | Colours palette-lock moved, and how far. A large ΔE means the palette lacks that colour. |
| pixelsChanged | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds substantial context beyond the annotations: ops execute in array order, paletteLock snaps to palette by CIELAB ΔE to avoid silently widening a curated palette, text is laid out and expanded to plain pixels before reaching Aseprite, and measureOnly computes ink bounds 'without touching the sprite'. The 'single undoable action' framing is consistent with destructiveHint=false rather than contradicting it.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the core purpose and batching rule, then moves to paletteLock, ordering, text/measureOnly, and grid. Dense but each sentence carries distinct guidance; the grid sentences are long and could be tightened, keeping it short of a 5.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a complex 9-param, 13-op tool with full schema coverage and an output schema, the description covers the non-obvious behaviors an agent must know: ordering, palette snapping, measure-only measurement, and the grid round-trip. Minor gap is no explicit mention of how blit/replace/gradient interact with selection or palette locking.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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: paletteLock's perceptual-snap purpose and its 'set false only when the user asked to introduce new colours', measureOnly's requirement that every op be text and its no-side-effect return, and the ordering guarantee for `ops`. Remaining op-specific params (blit, dither, gradient) are left to the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Apply a batch of drawing operations to one cel, as a single undoable action') and enumerates the op vocabulary. It also positions itself against the read-side sibling by referencing `look op="ascii"`, so an agent can distinguish it from transform/select without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives strong usage direction: 'Batch aggressively', 'a whole sprite in one call is normal and correct', and the read-modify-write workflow via `look op="ascii"` then grid. It names the read counterpart but stops short of explicit when-not-to-use guidance against mutating siblings like transform or recolor.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
exportExportADestructive
Write game-ready files. Ops: 'png' (single frame), 'gif' (animation), 'spritesheet' (packed sheet plus a JSON atlas with per-frame and per-tag data), 'frames' (numbered PNGs), 'aseprite' (save a copy of the source). Spritesheet is what an engine actually consumes: pass sheetType and byTag to control layout. Exporting does not save the working document — use sprite_manage op 'save' for that.
| Name | Required | Description | Default |
|---|---|---|---|
| op | Yes | ||
| path | Yes | Output file path. For 'frames', a pattern containing {frame}, e.g. 'walk_{frame}.png' — Aseprite expands it into one file per frame, numbered from 0. | |
| tags | No | Export only the frames these tags cover. gif, frames, spritesheet; 'png' and 'aseprite' refuse it. An unknown tag is refused. | |
| trim | No | Trim transparent margins; the atlas keeps the original offsets. | |
| byTag | No | Split the sheet by animation tag. | |
| frame | No | 1-based frame number. Omit to use the active frame. | |
| scale | No | Integer upscale, nearest-neighbour. | |
| layers | No | Export only these layers (names or group paths; a group brings its children). png, gif, frames, spritesheet; 'aseprite' refuses it. | |
| sprite | No | Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused. | |
| padding | No | Pixels between frames; prevents bleed at non-integer zoom. | |
| sheetType | No | Spritesheet layout. | horizontal |
| includeJson | No | Write a sibling JSON atlas for 'spritesheet'. |
Output Schema
| Name | Required | Description |
|---|---|---|
| op | Yes | |
| atlas | No | |
| files | Yes | |
| frame | No | Which frame a single-frame export wrote. Defaults to the active frame, which is not always the one you drew on. |
| width | No | |
| height | No | |
| sprite | Yes | |
| frameCount | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With destructiveHint=true already declared, the description adds real context: it discloses that export writes to disk but leaves the working document untouched, that the atlas preserves original offsets when trimmed, and that per-op option combinations are accepted or refused. It does not address overwrite behavior for an existing path, which is the one remaining destructive concern.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Four dense sentences, front-loaded with the action, then op enumeration, then the spritesheet recommendation, then the save-tool caveat. No filler and no repetition of schema content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The output schema covers return shapes, so covering them is unnecessary, and the description handles op semantics and the save distinction well. The only gap is that the destructive hint is left to the annotation without the description clarifying that an existing file at `path` may be overwritten.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 92%, so nearly every parameter is already documented in the schema (including trim offsets, frames pattern expansion, tags/layers per-op refusal). The description only repeats sheetType and byTag as the layout controls, adding no syntax beyond the schema. Baseline 3 is correct.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Write game-ready files') and then enumerates exactly what the five ops produce, including the artifacts (JSON atlas with per-frame and per-tag data, numbered PNGs, source copy). An agent can distinguish this from look/draw/sprite_manage 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes the agent: 'Exporting does not save the working document — use sprite_manage op save for that,' and names the condition that selects the default op ('Spritesheet is what an engine actually consumes'). The when-to-use and the alternative are both stated, not implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
frameFramesADestructive
Manage animation frames. Ops: 'list', 'add', 'duplicate', 'delete', 'set_duration', 'activate', 'reorder'. Durations are milliseconds per frame and carry most of the life in a cycle — hold a contact pose longer than a pass pose. Use count to add several at once and durations to set a whole cycle's timing in one call.
| Name | Required | Description | Default |
|---|---|---|---|
| op | Yes | ||
| count | No | ||
| frame | No | 1-based frame number. Omit to use the active frame. | |
| sprite | No | Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused. | |
| toIndex | No | For 'reorder': the 1-based position `frame` ends up at. Its cels and duration move with it; tag ranges stay where they are. | |
| linkCels | No | For 'duplicate': share the cel image instead of copying it, so edits apply to both. | |
| durations | No | Per-frame durations from frame 1, for 'set_duration'. | |
| afterFrame | No | Insert position. Default: at the end. | |
| durationMs | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| frames | No | |
| sprite | Yes | |
| frameCount | Yes | |
| activeFrame | No | |
| totalDurationMs | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds domain context about duration semantics but never says which specific ops are destructive/irreversible (delete) or what happens to existing frames on reorder — a meaningful gap for a multiplexed mutation tool. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with purpose, then ops, then parameter hints — a sensible order with no repetition. The artistic aside ('hold a contact pose longer than a pass pose') is mildly extraneous but small, and the rest of the text is tight.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained, and annotations cover the safety profile. For a 7-op multiplexed tool with one required param, the description is close to complete; the residual gap is that it does not map parameters to ops or flag which ops are irreversible.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 67%, and the description compensates by clarifying that durations are 'milliseconds per frame' (not stated in the durations schema description) and that `count` batches adds and `durations` sets a whole cycle in one call. This adds real operational meaning beyond the schema for the two least self-explanatory parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear resource ('animation frames') and enumerates the seven concrete operations, so an agent knows exactly what this tool covers. 'Manage' is somewhat generic as a verb, and no sibling (e.g. cel, tag, layer) is named for disambiguation, but the op list makes the scope unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Listing the ops implies when each is used, and the closing sentence says to use `count` for bulk adds and `durations` for whole-cycle timing. However, there is no explicit when-to-use versus sibling tools (cel/tag/layer), no prerequisites, and no guidance on which ops are destructive or when to prefer 'duplicate' with linkCels.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
layerLayersADestructive
Manage layers. Ops: 'list', 'create', 'rename', 'delete', 'reorder', 'set' (visibility/opacity/blend/lock), 'group', 'ungroup', 'merge', 'duplicate', 'activate'. Pass batch to run several in one undoable action — building a rig in one call is the normal use. 'duplicate' takes an optional toSprite to copy the layer's cels into another OPEN sprite instead of this one, by frame index; frames past the target's frame count are dropped and reported. A character that will be animated wants its parts on separate layers (head, torso, arm-far, arm-near, leg-far, leg-near) before any frames exist; splitting baked pixels apart later is far more work.
| Name | Required | Description | Default |
|---|---|---|---|
| op | No | Single operation. Use `batch` instead for several. | |
| name | No | ||
| batch | No | Operations applied in order, in one undoable action. Same shape as the single-op arguments. | |
| index | No | Target stack position for 'reorder'; 0 is bottom. | |
| names | No | For 'merge' and bulk 'group'. | |
| parent | No | Group layer to nest under. | |
| sprite | No | Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused. | |
| newName | No | ||
| opacity | No | ||
| visible | No | ||
| editable | No | ||
| toSprite | No | For 'duplicate': copy the layer into another OPEN sprite instead of this one. | |
| blendMode | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| layers | No | |
| sprite | Yes | |
| applied | No | |
| duplicated | No | Present when a 'duplicate' op in this call used `toSprite`. |
| activeLayer | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real behavioral detail beyond that: batch is a single undoable action, and duplicate-to-another-sprite drops and reports frames past the target's frame count.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loads the op list, then batch semantics, then the duplicate edge case, then a workflow tip. Efficient overall, though the final rigging-advice sentence is more ambient guidance than operational instruction.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Output schema exists so return values need no explanation, and annotations carry the destructive flag. However, with 13 parameters at 54% coverage, the description never says which parameters apply to which op (e.g. name vs newName, what 'set' can change), leaving ambiguity for a multi-mode tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 54%, so the schema documents some parameters while leaving others bare (name, newName, opacity, visible, editable have no descriptions). The description clarifies batch grouping, toSprite target semantics, and that 'set' covers visibility/opacity/blend/lock, but does not map the remaining params to their ops.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States the resource ('Manage layers') and enumerates all eleven operations, so an agent can see exactly what surface it covers. It clearly reads as the layer-level counterpart to siblings like cel and frame, though it never names a sibling to differentiate itself explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives concrete context: pass `batch` to run several ops in one undoable action and 'building a rig in one call is the normal use', plus the constraint that `duplicate`'s toSprite must be another OPEN sprite. No explicit when-not or named alternative tools, but the conditions that select the main modes are stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
lookLook at the spriteARead-only
See what is actually on the canvas. Ops:
• 'preview' — a nearest-neighbour upscaled PNG of the active frame (~1024px long edge). Use for overall read: silhouette, colour, whether it looks like the thing.
• 'ascii' — an exact text grid, one glyph per pixel with a colour legend and coordinate rulers. Use to verify precise pixel positions and values, to count cells, or on any client without vision. Reads up to the whole canvas; pass a region to crop. Glyphs are bound to palette indices, so every region and frame of a sprite agrees on what a glyph means; each read's legend lists only the colours it contains, so merge legends when rows from one piece go into another. Only colours outside the palette (listed in offPalette) get per-read glyphs. rulers=false prints the bare rows, which draw kind 'grid' takes back as-is: read a layer, edit the rows, send them at the same x/y.
• 'filmstrip' — every frame composited into one image. The only reliable way to review an animation, since a vision model reads just the first frame of a GIF.
• 'onion' — the target frame at full opacity over ghosted neighbouring frames, oldest-first. Use to check in-betweens and spacing while animating, without stepping through frames one at a time. Over an opaque background the target hides every ghost — pass layer to onion-skin just the part that moves.
• 'diff' — a pixel-level text diff between two frames: '.' unchanged, '-' erased, glyph = the new colour. Use it to confirm exactly what an edit touched.
• 'compare' — the reference layer (left, full opacity) beside the art without any reference layer (right), same frame, same scale. Use it when drawing from a concept or storyboard: name the few largest mismatches and fix only those.
Draw, then look, then fix. Do not report a sprite finished without looking at it.
| Name | Required | Description | Default |
|---|---|---|---|
| op | No | preview | |
| frame | No | 1-based frame number. Omit to use the active frame. | |
| layer | No | Read a single layer instead of the composited image. Honoured by preview, ascii, diff, filmstrip and onion; compare has its own `reference`. | |
| scale | No | Integer upscale for image ops, 1-128 (clamped so the output stays under ~2048px). Omit it — the automatic choice targets a ~1024px long edge, which is what a vision model can actually read. | |
| region | No | Crop. Omit to read the whole canvas. | |
| rulers | No | ascii: false drops the coordinate rulers and row labels, leaving rows you can edit and pass straight to `draw` kind 'grid' with the reported origin. | |
| sprite | No | Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused. | |
| toFrame | No | Diff: the later frame. | |
| fromFrame | No | Diff: the earlier frame. | |
| reference | No | Compare: the reference layer. Default 'reference'. | |
| framesAfter | No | Onion: ghost frames after the target. | |
| framesBefore | No | Onion: ghost frames before the target. | |
| ghostOpacity | No | Onion: opacity of the ghosted (non-target) frames. |
Output Schema
| Name | Required | Description |
|---|---|---|
| op | Yes | |
| rows | No | |
| text | No | The grid, for 'ascii' and 'diff'. |
| scale | No | |
| width | Yes | |
| frames | No | Filmstrip: frame count. |
| height | Yes | |
| legend | No | glyph → #rrggbb. Palette colours keep the same glyph across every read of the sprite. |
| origin | No | ascii: sprite position of the grid's top-left cell — the `x`/`y` for `draw` kind 'grid'. |
| sprite | Yes | |
| columns | No | |
| gridRows | No | ascii: the bare rows, '.' transparent — `draw` kind 'grid' `rows`, with `legend` and `origin`. |
| framesUsed | No | Onion: 1-based frame numbers composited. |
| offPalette | No | ascii/diff: glyphs whose colour is not in the palette. Their assignment can change between reads — do not reuse them across regions. |
| totalPixels | No | |
| changedBounds | No | Diff: tight bounding box of every changed pixel. Null when nothing changed. |
| changedPixels | No | |
| percentChanged | No | Diff: changed / total * 100. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish readOnly/no-open-world, but the description layers on substantial behavior: glyphs are bound to palette indices so regions agree, each legend lists only contained colours, off-palette colours get per-read glyphs, rulers=false output is reusable by draw kind 'grid', and onion ghosts are occluded by opaque backgrounds. This is detail an agent could not infer from annotations or schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the intent sentence, then a scannable bullet per op with bolded op names. It is long, but nearly every clause carries operational information; a few ascii details (legend merging, glyph binding) run longer than strictly necessary.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 13-param, six-mode read tool with an output schema already present, the description covers mode selection, crop/scale behavior, cross-tool round-tripping (ascii -> draw grid), and the animation-review caveat. Nothing an agent needs to invoke it correctly is missing, and return formats are appropriately left to the output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 92%, so the baseline is 3, but the description adds real meaning beyond it: what ascii/rulers output composes with, that scale defaults to a vision-readable ~1024px long edge, the crop semantics of region, and how layer/reference interact. It stops short of documenting fromFrame/toFrame and ghost opacity fully, leaving some to the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Opens with a specific verb+resource ('See what is actually on the canvas') and then enumerates six named ops, each described by what it renders, clearly separating this inspection tool from mutating siblings like draw and transform. An agent can tell exactly what it gets back per op 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Every op carries an explicit 'Use for…' clause ('total read: silhouette, colour', 'verify precise pixel positions', 'the only reliable way to review an animation', 'check in-betweens while animating', 'confirm exactly what an edit touched'). It also gives conditional caveats (opaque background hides ghosts, use vision-less clients with ascii) and a workflow rule: draw, then look, then fix.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
palettePaletteA
Read and shape the sprite's palette. Ops: • 'get' — current palette with per-colour usage counts. • 'set' — write specific indices, or replace the palette wholesale. • 'preset' — load a bundled palette by key: ~2000 of them, the classics (pico8, gameboy, cga, nes…) and the most-downloaded on Lospec (sweetie-16, endesga-32, resurrect-64, aap-64…). An unknown key or a name answers with the matching keys, so 'preset: "gameboy"' or 'preset: "endesga"' is a search. • 'load' — read a .gpl/.hex/.pal/.png palette file from disk. • 'ramp' — generate a hue-shifted ramp from a base colour and append it. Shadows rotate toward blue, highlights toward orange; a ramp that only changes brightness is the clearest tell of machine-made pixel art. • 'analyze' — report ramp structure, contrast, near-duplicate entries and colours used in the art that are not in the palette. • 'extract' — replace the palette with one quantized from the art itself (RGB sprites only). Use to derive a curated palette from a reference image imported at full colour. Decide the palette before drawing. Retro-fitting one onto finished art means repainting.
| Name | Required | Description | Default |
|---|---|---|---|
| op | Yes | ||
| base | No | Base colour for op 'ramp'. | |
| path | No | Palette file for op 'load'. | |
| steps | No | Ramp length. | |
| colors | No | For op 'set': the colours to write. | |
| preset | No | Preset key for op 'preset'. | |
| spread | No | How far the ramp reaches into shadow and light. | |
| sprite | No | Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused. | |
| replace | No | For op 'set'/'preset': replace the whole palette instead of merging. | |
| remapArt | No | When replacing a palette, repaint existing pixels to the nearest new colour instead of leaving them off-palette. | |
| maxColors | No | For op 'extract': target palette size. | |
| startIndex | No | For op 'set': where `colors` starts. Ignored when `replace` is true. |
Output Schema
| Name | Required | Description |
|---|---|---|
| op | Yes | |
| path | No | Palette file read by op 'load'. |
| ramp | No | |
| size | No | |
| total | No | Op 'preset' with no such key: presets bundled. |
| usage | No | |
| colors | No | |
| sprite | No | |
| matches | No | Op 'preset' with no such key: presets whose key, name, author or tags match it. |
| analysis | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With readOnlyHint=false the annotations already signal mutation; the description goes further by disclosing that 'extract' replaces the palette and is RGB-only, that 'ramp' appends rather than replaces, that presets search on unknown keys, and that remapping can repaint pixels. It does not state permission requirements or failure modes for load of bad files.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded summary sentence followed by a scannable bullet list keyed by op value, with zero filler. It is longer than most descriptions, but nearly every clause carries invocation-relevant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 12-parameter mutation tool with an output schema (so return values need no explanation) and annotations covering the safety profile, the description covers every op, the destructive side effects, and the sequencing convention. Nothing needed to invoke it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 92%, so the baseline is 3, but the description adds real meaning the schema cannot: a preset key may be a fuzzy name, ramp shadows rotate toward blue and highlights toward orange, and analyze reports off-palette colours. This meaningfully extends the structured fields.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Opens with a specific verb+resource ('Read and shape the sprite's palette') and then enumerates all seven ops with concrete semantics for each. An agent can tell this apart from siblings like recolor or transform 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives per-op guidance ('Use to derive a curated palette from a reference image'), a workflow rule ('Decide the palette before drawing. Retro-fitting one onto finished art means repainting'), and operational advice ('a preset name is a search'). However it never explicitly contrasts this tool with the closest sibling, recolor, which also changes colour; that exclusion is left to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
preflightPreflightARead-only
Check that Aseprite is connected and report what this session can do. Call this FIRST in any pixel-art task and stop if ready is false — every editing tool writes into the user's open Aseprite window ('live') or into a batch Aseprite this server owns ('headless'), and there is no useful fallback when that Aseprite is not there. Pass mode to choose which one the session works with from now on — only because the user asked (e.g. --headless) or the request plainly needs no window (files for CI, a batch of assets). Never switch to get around a live session that is not ready: ask the user instead. Switching loses nothing; each side keeps its documents.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | Switch the session to this Aseprite before checking. Omit to keep the current one. |
Output Schema
| Name | Required | Description |
|---|---|---|
| mode | Yes | 'live' = the user's open window. 'headless' = a batch Aseprite with no window; nothing is on disk until you save or export. |
| ready | Yes | True only when Aseprite is attached and accepting commands. |
| features | Yes | Optional capabilities this extension build supports. |
| switched | Yes | True when this call changed the session's mode. |
| directive | Yes | What to do next, in one sentence. |
| activeSprite | No | |
| asepriteVersion | No | |
| bridgeConnected | Yes | |
| pluginConnected | Yes | |
| extensionVersion | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description is genuinely rich about behavior — it explains that every editing tool writes into the live window or into a server-owned headless Aseprite, that there is no fallback, and that switching loses nothing because each side keeps its documents. However, it also states that passing mode changes what the session works with 'from now on', i.e. a persistent state mutation, which conflicts with the readOnlyHint=true annotation. The disclosure itself is strong, but it directly contradicts the structured safety hint, so this is flagged.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the action and the 'call FIRST' imperative, then the failure condition, then the mode guidance. It is longer than average but every sentence carries decision-relevant information; nothing is padding.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists (ready/capabilities), so return values need not be described. Combined with the safety, prerequisite, and mode-selection context the description supplies, an agent has everything needed to call this correctly first in a workflow.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the enum is documented, so the baseline is 3. The description adds meaning beyond the schema by explaining the consequence of the parameter ('which one the session works with from now on'), the conditions that justify switching, and the risk of switching for the wrong reason.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Check that Aseprite is connected and report what this session can do') and immediately positions itself as the mandatory entry point ('Call this FIRST in any pixel-art task'). An agent can distinguish it from every sibling editing tool without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit when-to-use ('FIRST in any pixel-art task'), when-to-stop ('stop if ready is false'), when to pass mode ('only because the user asked... or the request plainly needs no window'), and an explicit anti-pattern ('Never switch to get around a live session that is not ready: ask the user instead'). This is about as complete as usage guidance gets.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
read_pixelsRead pixelsARead-only
Read a rectangular region as structured data: a list of distinct colours plus a row-major index grid. Use this when you need to compute over pixels (sample a palette from art, find a silhouette edge, copy a region) rather than just look at them. For eyeballing, 'look' is cheaper.
| Name | Required | Description | Default |
|---|---|---|---|
| frame | No | 1-based frame number. Omit to use the active frame. | |
| layer | No | Layer name. Omit to use the active layer. | |
| region | No | Omit to read the whole canvas. | |
| sprite | No | Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused. | |
| composite | No | Read the flattened image. False reads only the target layer's cel. |
Output Schema
| Name | Required | Description |
|---|---|---|
| x | Yes | |
| y | Yes | |
| grid | Yes | Row-major indices into `colors`. |
| width | Yes | |
| colors | Yes | Distinct colours; index 0 is fully transparent. |
| height | Yes | |
| sprite | Yes | |
| uniqueColors | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the read-only behavior is known. The description adds value by describing the output structure ('a list of distinct colours plus a row-major index grid'), which goes beyond the annotation. It doesn't contradict annotations and provides useful context about the tool's non-mutating nature and return format.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise: two sentences that front-load the core function, then provide usage context and an alternative. Every word earns its place, with no redundancy or fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has an output schema (as indicated by context signals), the description does not need to detail return values. It covers purpose, usage, and differentiation from a key sibling. With read-only annotations and a fully documented parameter schema, the description is complete for an agent to select and invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% coverage with descriptions for all 5 parameters, including nested 'region' details. The tool description does not add any additional parameter-specific meaning beyond what the schema already provides. Per calibration, with high schema coverage, baseline is 3, and no extra param info is given, so this is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: 'Read a rectangular region as structured data: a list of distinct colours plus a row-major index grid.' It uses a specific verb (read) and resource (rectangular region), and explicitly differentiates from the sibling 'look' tool by contrasting computation vs. eyeballing. This allows an agent to distinguish it immediately.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit usage guidance: 'Use this when you need to compute over pixels (sample a palette from art, find a silhouette edge, copy a region) rather than just look at them. For eyeballing, 'look' is cheaper.' This clearly states when to use this tool and when to use an alternative, leaving no ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
recolorRecolorA
Change colours in a region by intent, staying palette-legal. Ops: • 'shade' — darken or lighten with proper hue shifting (shadows cool, highlights warm). Use this instead of picking a darker hex by hand. • 'snap' — pull off-palette pixels onto the nearest palette colour by perceptual (CIELAB) distance. • 'replace' — swap one exact colour for another. • 'hue_shift' — rotate hue, e.g. to make a colour variant of a finished sprite. • 'desaturate' — drop toward grey, useful for a value check. Operates on a region's distinct colours in one pass, so a 64×64 recolour is one undo step, not four thousand.
| Name | Required | Description | Default |
|---|---|---|---|
| op | Yes | ||
| to | No | For 'replace'. | |
| from | No | For 'replace'. | |
| frame | No | 1-based frame number. Omit to use the active frame. | |
| layer | No | Layer name. Omit to use the active layer. | |
| amount | No | For 'shade': negative darkens, positive lightens. One ramp step is roughly 0.15. | |
| region | No | Omit to affect the whole cel. | |
| sprite | No | Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused. | |
| degrees | No | For 'hue_shift'. | |
| strength | No | For 'desaturate'. | |
| selectionOnly | No | ||
| clampToPalette | No | Snap the result back onto the palette. Turn off only when growing the palette deliberately. |
Output Schema
| Name | Required | Description |
|---|---|---|
| op | Yes | |
| sprite | Yes | |
| mapping | Yes | Exactly which colour became which, and how many pixels each move touched. |
| pixelsChanged | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description goes beyond annotations by explaining behavioral details: operations run in one pass so a 64×64 recolour is one undo step, and it emphasizes palette legality and the clampToPalette option. It also clarifies that shade does proper hue shifting (shadows cool, highlights warm). Annotations indicate it's not read-only, which aligns with the mutation described. No contradictions, and the description adds valuable context about how the tool behaves.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is structured with a clear opening statement followed by a bulleted list of ops, making it scannable. While it is fairly long, each sentence adds information about operations or parameters. The front-loaded purpose and op list help an agent quickly grasp the tool's scope. Some redundancy exists (e.g., palette-legal mentioned twice), but overall it's efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity (12 parameters, nested region object), the description is remarkably complete: it explains each op's use case, relevant parameters, and notes on palette behavior and undo granularity. The output schema is present, so return values are covered elsewhere. It could mention edge cases like invalid colors or when clampToPalette might fail, but for an agent deciding to call the tool, it's sufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is high (83%), but the description adds crucial meaning: it explains the amount parameter with 'negative darkens, positive lightens. One ramp step is roughly 0.15,' defines from/to for replace, and clarifies clampToPalette's role in palette growth. These enrich the raw schema and help an agent select correct parameter values without needing extra inference.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Change colours in a region by intent, staying palette-legal.' It then enumerates specific operations (shade, snap, replace, hue_shift, desaturate) with examples, making it obvious what the tool does and how it differs from manual color editing. It's specific and distinct from sibling tools like draw or transform.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides explicit guidance for each operation, e.g., 'Use this instead of picking a darker hex by hand' for shade, and 'useful for a value check' for desaturate. However, it does not explicitly mention alternative tools or when NOT to use recolor in favor of another sibling, so it's not fully exhaustive but gives solid contextual usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
referenceReference imageA
Bring an external image into the sprite as a reference layer, so you can trace proportions or sample colours from it. Ops: 'import' (place an image on a locked, semi-transparent layer above the art), 'sample_palette' (read its dominant colours without importing), 'list', 'remove'. A concept sheet or storyboard arrives as one image: region crops one panel of it, and grid cuts it into panels and puts panel i on frame i of a single reference layer, so each animation frame is drawn over its own storyboard panel. Importing at a different size uses nearest-neighbour; a reference scaled down to 32×32 is a guide for proportion and pose, never a finished sprite.
| Name | Required | Description | Default |
|---|---|---|---|
| x | No | ||
| y | No | ||
| op | Yes | ||
| fit | No | How to size the image (or each panel) against the canvas. | contain |
| grid | No | Import a storyboard: split the (cropped) source into equal panels and place panel i on frame `frame`+i-1 of one reference layer. The sprite must already have enough frames. | |
| name | No | Layer name. Default: 'reference'. | |
| path | No | Image file to read. | |
| frame | No | Import: the frame the image — or the first `grid` panel — lands on. Default: the active frame, or frame 1 with `grid`. | |
| colors | No | For 'sample_palette'. | |
| region | No | Use only this rectangle of the SOURCE image, in its own pixels — one panel of a concept sheet. Applies to 'import' and 'sample_palette'. | |
| sprite | No | Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused. | |
| opacity | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| op | Yes | |
| layer | No | |
| width | No | |
| frames | No | Import: the frames that received a reference cel. |
| height | No | |
| panels | No | Import: how many panels were placed. |
| sprite | Yes | |
| palette | No | Dominant colours with their share of the image. |
| references | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare readOnlyHint=false and openWorldHint=false; the description adds real behavior: import lands on a locked, semi-transparent layer above the art; resizing uses nearest-neighbour; a 32×32 reference is a proportion guide, never a finished sprite; grid requires the sprite to already have enough frames. Missing specifics like whether 'remove' is reversible, but coverage is strong.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the core purpose, then the op list, then the storyboard/grid mechanism, then the scaling caveat. Dense and mostly waste-free, though the panel-index explanation is slightly elaborate for the space it consumes.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need no explanation, and the description covers the four ops, region, and grid for a 12-param nested tool. Gaps remain around 'list'/'remove' semantics and the 'fit'/'opacity' parameters, but nothing critical to correct invocation is absent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 67% schema coverage and 12 params, the description meaningfully supplements the schema: 'region' crops one panel of the SOURCE image, 'grid' places panel i on frame i of one reference layer, and import's scaling behavior is explained. It does not unpack the 'fit' enum values (contain/cover/stretch) or 'colors'/'opacity' effects, which remains a gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States the specific resource (external image as reference layer) and enumerates the four ops ('import', 'sample_palette', 'list', 'remove') with a one-clause gloss of each. An agent can distinguish this from the sibling 'layer', 'palette', and 'look' tools without opening any schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives clear when-to-use context per op: 'sample_palette' reads colours 'without importing', 'region' handles a single panel of a concept sheet, 'grid' handles a storyboard. It never names an alternative tool (e.g. why not use 'palette' to sample colours), so it stops short of the 5 bar.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
selectSelectionAIdempotent
Read or change the active selection. Ops: 'get', 'none', 'all', 'rect', 'ellipse', 'color' (select every pixel matching a colour), 'invert', 'grow', 'shrink'. A selection scopes draw, transform and recolor, which is usually cheaper and safer than masking by hand.
| Name | Required | Description | Default |
|---|---|---|---|
| op | Yes | ||
| mode | No | How this selection combines with the existing one. | replace |
| rect | No | ||
| color | No | For op 'color'. | |
| frame | No | 1-based frame number. Omit to use the active frame. | |
| layer | No | Layer name. Omit to use the active layer. | |
| amount | No | Pixels, for grow/shrink. | |
| sprite | No | Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused. | |
| tolerance | No | Largest per-channel difference (0–255) still counted as the clicked colour. RGB sprites only; indexed and grayscale fills stay exact. | |
| contiguous | No | For op 'color'. |
Output Schema
| Name | Required | Description |
|---|---|---|
| empty | Yes | |
| bounds | No | |
| sprite | Yes | |
| pixelCount | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=false, idempotentHint=true and openWorldHint=false, so safety/idempotency are already covered. The description adds genuinely new behavioral context: a selection is state that scopes draw, transform and recolor, which explains the side effects of this tool on other tools. It doesn't say what happens to a prior selection under each op, but with annotations present this is solid added value.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three tight sentences: purpose first, op inventory second, rationale third. Zero filler; every clause carries information an agent needs.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema, annotations and a richly described 10-parameter schema, the description covers the conceptual surface well. Its only notable gap is that it never links ops to their required parameters (e.g., rect needs 'rect', color needs 'color'/tolerance/contiguous), which the agent must infer from the schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 80%, so most parameters (mode, frame, layer, amount, sprite, tolerance, contiguous) are already documented — baseline 3. The description goes beyond by explaining the meaning of each op value, including that 'color' selects every pixel matching a colour, which the enum alone does not convey.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource ('Read or change the active selection') and then enumerates all nine ops with brief semantics for the non-obvious ones ('color' = every pixel matching a colour). An agent can distinguish this from draw, transform, recolor and read_pixels without opening any schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides a clear rationale for using selections: 'A selection scopes draw, transform and recolor, which is usually cheaper and safer than masking by hand.' That tells the agent when a selection is the right mechanism, but it gives no explicit exclusions or routing between ops (e.g., get vs read_pixels) and no prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
sprite_infoSprite infoARead-only
Full structured state of a sprite: dimensions, colour mode, palette, every layer (with opacity, blend mode, visibility, group nesting), every frame with its duration, animation tags, slices and the current selection. Read this before editing — guessing at layer names or frame counts is the most common way an agent corrupts someone's file.
| Name | Required | Description | Default |
|---|---|---|---|
| sprite | No | Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused. | |
| includeSlices | No | ||
| includePalette | No | Include the full palette as hex. |
Output Schema
| Name | Required | Description |
|---|---|---|
| id | Yes | Stable id for this open document. Pass it back as '#<id>'. |
| name | Yes | |
| tags | Yes | |
| width | Yes | |
| frames | Yes | |
| height | Yes | |
| layers | Yes | |
| slices | No | |
| palette | No | |
| filename | No | |
| modified | Yes | Unsaved changes present in this document. |
| colorMode | Yes | |
| selection | No | |
| frameCount | Yes | |
| activeFrame | No | |
| activeLayer | No | |
| transparentIndex | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally; the description adds the operational insight that this is a mandatory pre-edit read to avoid corrupting state. It does not add auth, rate-limit, or cost context, but for a local read-only tool that is a minor omission.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tightly written sentences, front-loaded with the resource and its contents, with the rationale for use placed last as a motivation rather than filler. The field enumeration slightly overlaps the output schema but remains useful for matching this tool against siblings.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, the description correctly avoids explaining return values and instead covers scope, contents, and the pre-edit workflow. It leaves `includeSlices` unexplained, but the only remaining gap is minor for a zero-required-parameter read tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 67%: `sprite` and `includePalette` carry their own schema descriptions, while `includeSlices` is undocumented. The prose only indirectly alludes to slices and palette ('slices and the current selection'), adding no format or default semantics beyond the schema. Baseline 3 is appropriate since the schema does most of the work.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource ('Full structured state of a sprite') and enumerates the exact contents: dimensions, colour mode, palette, layers with opacity/blend/visibility/nesting, frames with durations, tags, slices, and selection. This is far more specific than sibling inspection tools and lets an agent tell it apart from `look`, `validate`, or `layer` without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly prescribes when to use it: 'Read this before editing,' with a concrete failure mode ('guessing at layer names or frame counts is the most common way an agent corrupts someone's file'). It does not name an alternative inspection sibling (e.g. `look` or `validate`) or state when not to use it, 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.
sprite_manageManage spritesADestructive
Open, create, focus, resize, save and close sprites in the running Aseprite session. Ops: 'list' (open documents), 'new', 'open', 'activate', 'save', 'save_as', 'close', 'resize_canvas', 'set_properties', 'slice_create', 'slice_update', 'slice_delete'. Canvas resize keeps existing pixels — pass an anchor to say where they land. Slices name a rectangular region of the canvas for an engine to read back — a 9-patch panel's center, or a hotspot's pivot.
| Name | Required | Description | Default |
|---|---|---|---|
| op | Yes | ||
| name | No | Slice name. Required for 'slice_create'; identifies it for update/delete. | |
| path | No | File path for 'open' and 'save_as'. | |
| color | No | For slice ops: slice colour in the timeline, #rrggbb. | |
| force | No | Allow 'close' to discard unsaved changes. Ask the user before setting this. | |
| pivot | No | For slice ops. | |
| width | No | ||
| anchor | No | Where existing pixels sit after 'resize_canvas'. | center |
| bounds | No | Slice rectangle. Required for 'slice_create'. | |
| center | No | For slice ops: nine-slice centre region, relative to `bounds`. | |
| height | No | ||
| sprite | No | Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused. | |
| colorMode | No | For 'new'. Indexed keeps a sprite honest about its palette. | |
| pixelAspect | No | e.g. '1:1' or '1:2'. |
Output Schema
| Name | Required | Description |
|---|---|---|
| id | No | Stable id of the affected document; pass it back as '#<id>'. |
| op | Yes | |
| name | No | Slice name, for 'slice_delete'. |
| path | No | |
| slice | No | The affected slice, for 'slice_create'/'slice_update'. |
| width | No | |
| height | No | |
| sprite | No | |
| sprites | No |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is carried by structured data. The description adds useful operational context beyond that ('Canvas resize keeps existing pixels', what slices are for), but it never says which ops are the destructive ones (close/save), nor that ops act on a session-bound focused sprite. Solid addition, not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three dense sentences, front-loaded with the verb/resource scope before the op list and the two clarifying notes. Every sentence contributes (op inventory, resize behaviour, slice semantics); no filler, though the op list is long by necessity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 14-parameter, 12-op multiplexed tool with nested objects and an output schema, the description gives an adequate map: full op inventory plus targeted clarifications for the two least obvious families (resize anchor, slices). It stops short of per-op parameter pairing, but the schema's per-field op hints largely cover that.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is a high 79%, so the baseline is 3, and the description genuinely adds meaning beyond it: the anchor parameter's effect on where existing pixels land, and the purpose of slice fields (nine-slice 'center', hotspot 'pivot'). It clarifies semantics of ops-scoped parameters rather than just restating names.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Opens with a specific verb list and resource ('Open, create, focus, resize, save and close sprites in the running Aseprite session') and enumerates all 12 supported ops, so the agent knows the exact capability surface. It does not, however, name or differentiate itself from close siblings like sprite_info, transform, or look, leaving that routing to inference.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied through the op enumeration and one conditional note ('Omit to use the sprite Aseprite has focused'). There is no explicit when-to-use-this-vs-alternative guidance, e.g. why resize_canvas here rather than transform, or when to prefer sprite_info over 'list'. A capable agent can infer intent from op names, but nothing routes it deliberately.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
tagAnimation tagsADestructive
Manage animation tags — the named frame ranges a game engine imports as 'idle', 'walk', 'attack'. Ops: 'list', 'create', 'update', 'delete'. Tag every cycle before export; an untagged spritesheet is a pile of frames the engine cannot address.
| Name | Required | Description | Default |
|---|---|---|---|
| op | Yes | ||
| to | No | Last frame, 1-based, inclusive. | |
| from | No | First frame, 1-based, inclusive. | |
| name | No | ||
| color | No | Tag colour in the timeline, #rrggbb. | |
| sprite | No | Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused. | |
| newName | No | ||
| repeats | No | Loop count; 0 means forever. | |
| direction | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| tags | Yes | |
| sprite | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already indicate destructiveHint=true and readOnlyHint=false, so the agent is aware this can modify state. The description adds that untagged spritesheets are unusable by the engine, but it does not disclose behavioral details such as immediate persistence or side effects of update/delete. This is adequate but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact, front-loaded with the core concept, and every sentence earns its place. The first sentence defines the resource and operations, and the second gives a practical workflow warning without padding.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers what tags are and why they matter, and the schema provides parameter details. However, it does not clarify which parameters are required for each operation (e.g., create vs. delete vs. update), which is a notable gap for correct invocation. Output schema exists, so return-value documentation is not the missing piece.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents several parameters (from, to, color, sprite, repeats), while 'name' and 'newName' benefit only from the description's 'named frame ranges' context. With 56% schema coverage, the description adds some conceptual meaning but does not fully compensate for the undocumented parameters or op-specific requirements.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool manages animation tags (named frame ranges) and enumerates the supported operations: list, create, update, delete. It uses concrete examples like 'idle', 'walk', 'attack' to make the resource unambiguous. It does not explicitly differentiate from sibling tools, but the resource and examples make the purpose clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives a clear workflow cue: 'Tag every cycle before export', and explains why tagging matters. It does not explicitly state when not to use this tool or point to alternatives among the siblings, so it stops short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
tilesetTilesetsA
Work with Aseprite tilemap layers. Ops:
• 'list' — tilesets in the sprite.
• 'create_layer' — a new empty tilemap layer on a given grid.
• 'get' — tile count and, with a path, the tiles as one packed PNG.
• 'stamp' — place tiles by grid coordinate. x/y are grid cells, not pixels.
• 'pack' — turn a hand-painted mockup layer into a tileset plus a tilemap that reconstructs it exactly. Deduplicates identical cells; tolerance also merges near-identical ones. The canvas must be a whole number of tiles, and the source layer is hidden rather than deleted so you can compare.
• 'export' — writes the packed PNG plus the file the engine reads: 'tiled' (.tsj tileset and a .tmj map that uses it), 'godot' (Godot 4 .tres TileSet), or 'json' (tile grid plus the tilemap layout).
Painting a level by hand and packing it produces better tilesets than authoring tiles in isolation, because you see the whole picture while drawing. layout: 'blob47' adds a Tiled wangset for autotiling, and assumes the tileset is authored in canonical blob47 order after the empty tile — it refuses rather than writing a wangset that would autotile wrongly. Requires an extension build advertising the 'tileset' feature — check preflight first.
| Name | Required | Description | Default |
|---|---|---|---|
| op | Yes | ||
| name | No | ||
| path | No | Output path for 'export' and 'get'. | |
| frame | No | 1-based frame number. Omit to use the active frame. | |
| layer | No | Layer name. Omit to use the active layer. | |
| tiles | No | For 'stamp'. x/y are tile-grid cells, not pixels. | |
| format | No | tiled | |
| layout | No | Autotile layout for 'export'. | grid |
| sprite | No | Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused. | |
| tileWidth | No | ||
| tolerance | No | For 'pack': maximum per-channel difference at which two cells count as the same tile. 0 means exact, which is also much faster — anything above 0 compares every cell against every tile found so far. | |
| tileHeight | No |
Output Schema
| Name | Required | Description |
|---|---|---|
| op | Yes | |
| rows | No | |
| files | No | |
| layer | No | |
| format | No | |
| layout | No | |
| sprite | Yes | |
| columns | No | |
| skipped | No | For 'stamp': placements outside the grid or naming a tile that does not exist. |
| tilesets | No | |
| cellCount | No | For 'pack': grid cells examined. |
| tileCount | No | |
| tileWidth | No | |
| tileHeight | No | |
| reusedExact | No | For 'pack': cells that matched an existing tile exactly. |
| reusedFuzzy | No | For 'pack': cells merged by `tolerance`. A high number here with a low tolerance means the mockup has near-duplicate tiles worth cleaning up. |
| sourceLayer | No | For 'pack': the mockup layer, now hidden. |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only set readOnlyHint=false and openWorldHint=false, leaving the description to carry behavioral detail. It discloses non-obvious behaviors: 'stamp' uses grid cells not pixels, 'pack' deduplicates and hides (not deletes) the source layer, 'blob47' refuses when ordering is wrong, and 'tolerance' has performance implications. This goes well beyond the schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is long but appropriately so for a multi-operation tool. It front-loads the purpose, then lists ops in a scannable bullet format, and adds a rationale paragraph at the end. Every sentence serves a purpose, with no filler. It could be slightly more compact, but the structure aids readability.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 12 parameters and six operations, the description covers most critical details: output formats, grid semantics, preconditions, and error behavior. An output schema exists (per context), which likely covers return structures. Minor gaps include exact return values for 'list' and 'create_layer', but these are not critical for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 58%, so the description must compensate for undocumented parameters. It explains 'tolerance', 'layout', 'sprite', and 'tiles' in detail, and clarifies grid-vs-pixel semantics. While 'name', 'tileWidth', and 'tileHeight' lack description-level context, they are straightforward from the schema defaults and bounds. The description meaningfully enhances understanding of the complex parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description begins with 'Work with Aseprite tilemap layers' and then enumerates six distinct operations (list, create_layer, get, stamp, pack, export). It clearly states what the tool does and each op has a specific verb and resource. It distinguishes itself from sibling tools like 'layer' and 'export' by focusing on tileset-specific functionality, so an agent can immediately understand its scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear guidance on when to use the 'pack' operation ('Painting a level by hand and packing it produces better tilesets than authoring tiles in isolation') and warns about prerequisites ('Requires an extension build advertising the 'tileset' feature — check preflight first'). It does not explicitly contrast with sibling tools like 'layer' or 'export', but the internal op routing is clear and context is sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
transformTransformA
Move, flip, rotate or scale pixels on ONE cel — the target layer's image on the target frame. Ops: 'translate', 'flip', 'rotate', 'scale', 'outline', 'crop_to_content'. To transform part of a cel, crop the region out with draw op 'blit' first; there is no selection-scoped transform. Rotation is only clean at 90° multiples — arbitrary angles destroy pixel art, so anything else needs allowLossy. Scaling is nearest-neighbour and integer-only for the same reason.
| Name | Required | Description | Default |
|---|---|---|---|
| dx | No | ||
| dy | No | ||
| op | Yes | ||
| axis | No | For 'flip'. | |
| side | No | For 'outline'. 'outside' paints transparent pixels touching opaque ones, growing the cel by one pixel each way. 'inside' recolours opaque pixels that touch transparency instead, same size in and out. | outside |
| angle | No | Degrees, clockwise. For 'rotate'. | |
| color | No | Outline colour, for 'outline'. | |
| frame | No | 1-based frame number. Omit to use the active frame. | |
| layer | No | Layer name. Omit to use the active layer. | |
| factor | No | For 'scale'. | |
| sprite | No | Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused. | |
| diagonals | No | For 'outline'. Treat diagonal neighbours as touching too (8-neighbour instead of 4). | |
| thickness | No | ||
| allowLossy | No | Permit a non-90° rotation or non-integer scale. Ask the user first. |
Output Schema
| Name | Required | Description |
|---|---|---|
| op | Yes | |
| bounds | No | |
| sprite | Yes | |
| pixelsChanged | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the mutation/read profile, and the description adds meaningful behavioral context on top: rotation is clean only at 90° multiples, arbitrary angles 'destroy pixel art' and require `allowLossy`, and scaling is nearest-neighbour and integer-only. This is genuinely useful operational disclosure beyond the annotation trio. It does not describe output or failure modes, keeping it from a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, front-loaded with the verb/resource/scope, then the op list, then the two constraints. Every clause carries information (no selection transform, lossy gating, integer scaling) with no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 14-parameter mutation tool with an output schema present, the description covers scope, ops, lossy caveats and the partial-transform workaround adequately. Minor gaps remain, e.g. how translation handles out-of-bounds pixels (clip vs wrap) and the default outline color, but nothing blocking correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 71%, so the schema documents most parameters (axis, side, angle, color, factor, sprite, diagonals, allowLossy). The description still adds value by defining op-level semantics and the integer/90° constraints that explain why `factor` is integer-only and why `allowLossy` exists, which the schema's max/min bounds alone do not convey.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Opens with a specific verb set and resource ('Move, flip, rotate or scale pixels on ONE cel'), scopes it precisely to 'the target layer's image on the target frame', and enumerates the six ops. It also distinguishes itself from siblings by naming `draw` and ruling out any selection-scoped transform, so an agent can tell it apart from `select`/`draw` without opening schemas.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives a concrete when-not case and a workaround: partial transforms must go through `draw` op 'blit' because 'there is no selection-scoped transform'. It also gates lossy behavior behind `allowLossy` with an explicit 'Ask the user first'. No explicit statement of the ordinary when-to-use happy path, but the boundaries are clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
validateValidateARead-only
Lint a sprite against pixel-art rules and report concrete, located problems. Checks: off-palette colours, orphan/stray pixels, broken or doubled outlines, banding, semi-transparent (soft or resized) pixels, empty layers, untagged frames and uniform frame timing; expect adds per-layer frame ranges and layers that must not overlap. Symmetry and cross-frame volume drift are not checked — judge those with look op 'ascii' and 'filmstrip'. Run this before telling the user a sprite is finished. It answers 'is this actually done' with evidence rather than optimism.
| Name | Required | Description | Default |
|---|---|---|---|
| checks | No | Omit to run everything. | |
| expect | No | The animation contract you already know. Runs independently of `checks`, whenever given: flags art outside a layer's expected frame ranges (or a missing cel inside one), and any frame where two named layers' opaque pixels overlap. | |
| sprite | No | Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused. | |
| strict | No | Treat style warnings as failures. Use when the user asked for a specific discipline. |
Output Schema
| Name | Required | Description |
|---|---|---|
| score | Yes | |
| passed | Yes | |
| sprite | Yes | |
| summary | Yes | |
| findings | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare readOnlyHint/openWorldHint, so the description carries the disclosure burden, and it does so well: it lists exactly what is inspected, what `expect` enforces, and explicitly states the tool is evidence-based rather than optimistic. It stops short of describing the report shape, but an output schema covers that.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the core verb and check list, then the exclusion note, then the usage directive. Dense but every sentence carries information; only the closing 'evidence rather than optimism' is mild flourish.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 4-parameter read-only tool with full schema coverage and an output schema, the description supplies everything needed: what it checks, the `expect` semantics, what it deliberately omits, and when to run it. The main residual gap is the relationship to the sibling 'preflight'.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3, but the description adds real meaning to the `checks` enum by spelling out what each category (palette, strays, outline, banding, antialiasing, layers, animation) actually detects, plus the `expect` contract semantics. This goes beyond the enum strings alone.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource ('Lint a sprite against pixel-art rules') and enumerates the exact checks performed (off-palette colours, strays, broken outlines, banding, etc.). It also distinguishes itself from the 'look' op by naming what it does NOT check (symmetry, cross-frame volume drift), so an agent can separate it from siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives an explicit trigger ('Run this before telling the user a sprite is finished') and routes the uncovered concerns to a named alternative. However it does not differentiate from the sibling 'preflight', which likely overlaps with the 'export_readiness' check — that ambiguity is left unresolved.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
v0.8.2- Changed
palette3 fields changed- removed
Output schema / properties / availablePresetsRemoved value: -{ - "items": { - "additionalProperties": false, - "properties": { - "key": { - "type": "string" - }, - "name": { - "type": "string" - }, - "notes": { - "type": "string" - }, - "size": { - "type": "integer" - } - }, - "required": [ - "key", - "name", - "size", - "notes" - ], - "type": "object" - }, - "type": "array" -} - added
Output schema / properties / matchesAdded value: +{ + "description": "Op 'preset' with no such key: presets whose key, name, author or tags match it.", + "items": { + "additionalProperties": false, + "properties": { + "author": { + "type": "string" + }, + "key": { + "type": "string" + }, + "name": { + "type": "string" + }, + "notes": { + "type": "string" + }, + "size": { + "type": "integer" + } + }, + "required": [ + "key", + "name", + "author", + "size" + ], + "type": "object" + }, + "type": "array" +} - added
Output schema / properties / totalAdded value: +{ + "description": "Op 'preset' with no such key: presets bundled.", + "type": "integer" +}
- Changed
sprite_info2 fields changed- added
Output schema / properties / modifiedAdded value: +{ + "description": "Unsaved changes present in this document.", + "type": "boolean" +} - changed
Output schema / requiredPrevious value: -[ - "id", - "name", - "width", - "height", - "colorMode", - "frameCount", - "layers", - "frames", - "tags" -]New value: +[ + "id", + "name", + "width", + "height", + "colorMode", + "frameCount", + "modified", + "layers", + "frames", + "tags" +]
2 tool updates
v0.7.0- Changed
draw1 field changed- changed
Input schema / properties / ops / items / anyOfPrevious value: -[ - { - "additionalProperties": false, - "properties": { - "color": { - "description": "Colour as #rrggbb or #rrggbbaa.", - "pattern": "^#?([0-9a-fA-F]{6}|[0-9a-fA-F]{8})$", - "type": "string" - }, - "kind": { - "const": "pixels", - "type": "string" - }, - "points": { - "items": { - "additionalProperties": false, - "properties": { - "color": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color", - "description": "Per-pixel colour. Falls back to the op's `color`." - }, - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - }, - "maxItems": 20000, - "minItems": 1, - "type": "array" - } - }, - "required": [ - "kind", - "points" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "color": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "from": { - "additionalProperties": false, - "properties": { - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - }, - "kind": { - "const": "line", - "type": "string" - }, - "thickness": { - "default": 1, - "exclusiveMinimum": 0, - "maximum": 64, - "type": "integer" - }, - "to": { - "additionalProperties": false, - "properties": { - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - } - }, - "required": [ - "kind", - "color", - "from", - "to" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "closed": { - "default": false, - "type": "boolean" - }, - "color": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "fill": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color", - "description": "Fill colour; only meaningful when closed." - }, - "kind": { - "const": "polyline", - "type": "string" - }, - "points": { - "items": { - "additionalProperties": false, - "properties": { - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - }, - "minItems": 2, - "type": "array" - } - }, - "required": [ - "kind", - "color", - "points" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "color": { - "description": "Outline colour.", - "pattern": "^#?([0-9a-fA-F]{6}|[0-9a-fA-F]{8})$", - "type": "string" - }, - "fill": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color", - "description": "Omit for an outline only." - }, - "kind": { - "const": "rect", - "type": "string" - }, - "rect": { - "additionalProperties": false, - "properties": { - "height": { - "exclusiveMinimum": 0, - "type": "integer" - }, - "width": { - "exclusiveMinimum": 0, - "type": "integer" - }, - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y", - "width", - "height" - ], - "type": "object" - } - }, - "required": [ - "kind", - "color", - "rect" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "color": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "fill": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color", - "description": "Colour as #rrggbb or #rrggbbaa." - }, - "kind": { - "const": "ellipse", - "type": "string" - }, - "rect": { - "additionalProperties": false, - "description": "Bounding box of the ellipse.", - "properties": { - "height": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/height" - }, - "width": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/width" - }, - "x": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/x" - }, - "y": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/y" - } - }, - "required": [ - "x", - "y", - "width", - "height" - ], - "type": "object" - } - }, - "required": [ - "kind", - "color", - "rect" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "at": { - "additionalProperties": false, - "properties": { - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - }, - "color": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "contiguous": { - "default": true, - "type": "boolean" - }, - "kind": { - "const": "fill", - "type": "string" - }, - "tolerance": { - "default": 0, - "description": "Largest per-channel difference (0–255) still counted as the clicked colour. RGB sprites only; indexed and grayscale fills stay exact.", - "maximum": 255, - "minimum": 0, - "type": "integer" - } - }, - "required": [ - "kind", - "color", - "at" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "from": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "kind": { - "const": "replace", - "type": "string" - }, - "region": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect" - }, - "to": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - } - }, - "required": [ - "kind", - "from", - "to" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "colorA": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "colorB": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "kind": { - "const": "dither", - "type": "string" - }, - "pattern": { - "default": "bayer4", - "enum": [ - "checker", - "bayer2", - "bayer4", - "bayer8", - "noise" - ], - "type": "string" - }, - "ratio": { - "default": 0.5, - "description": "0 = all colorA, 1 = all colorB.", - "maximum": 1, - "minimum": 0, - "type": "number" - }, - "rect": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect" - } - }, - "required": [ - "kind", - "rect", - "colorA", - "colorB" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "direction": { - "default": "vertical", - "enum": [ - "vertical", - "horizontal", - "diagonal", - "radial" - ], - "type": "string" - }, - "dither": { - "default": false, - "description": "Dither the band boundaries.", - "type": "boolean" - }, - "from": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "kind": { - "const": "gradient", - "type": "string" - }, - "rect": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect" - }, - "steps": { - "default": 4, - "description": "Banded, not smooth — a smooth gradient is not pixel art.", - "maximum": 64, - "minimum": 2, - "type": "integer" - }, - "to": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - } - }, - "required": [ - "kind", - "rect", - "from", - "to" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "kind": { - "const": "clear", - "type": "string" - }, - "region": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect", - "description": "Omit to clear the whole cel." - } - }, - "required": [ - "kind" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "flipHorizontal": { - "default": false, - "type": "boolean" - }, - "flipVertical": { - "default": false, - "type": "boolean" - }, - "from": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect" - }, - "fromFrame": { - "exclusiveMinimum": 0, - "type": "integer" - }, - "fromLayer": { - "type": "string" - }, - "kind": { - "const": "blit", - "type": "string" - }, - "skipTransparent": { - "default": true, - "type": "boolean" - }, - "to": { - "additionalProperties": false, - "properties": { - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - } - }, - "required": [ - "kind", - "from", - "to" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "anchor": { - "default": "top_left", - "description": "Resolved against the glyph ink box, not the full advance box — outline and shadow never shift it.", - "enum": [ - "top_left", - "top", - "top_right", - "left", - "center", - "right", - "bottom_left", - "bottom", - "bottom_right", - "baseline_left", - "baseline", - "baseline_right" - ], - "type": "string" - }, - "bold": { - "default": 0, - "description": "Grid-cell passes grown rightward; 0 is regular weight.", - "maximum": 3, - "minimum": 0, - "type": "integer" - }, - "color": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "font": { - "default": "pixel5x7", - "description": "Name in knowledge/fonts, without the .json extension.", - "type": "string" - }, - "kind": { - "const": "text", - "type": "string" - }, - "letterSpacing": { - "default": 1, - "type": "integer" - }, - "lineSpacing": { - "default": 1, - "type": "integer" - }, - "outlineColor": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color", - "description": "Colour as #rrggbb or #rrggbbaa." - }, - "outlineDiagonals": { - "default": true, - "description": "8-neighbour outline instead of 4.", - "type": "boolean" - }, - "scale": { - "default": 1, - "maximum": 8, - "minimum": 1, - "type": "integer" - }, - "shadowColor": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color", - "description": "Colour as #rrggbb or #rrggbbaa." - }, - "shadowOffset": { - "additionalProperties": false, - "default": { - "x": 1, - "y": 1 - }, - "properties": { - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - }, - "text": { - "description": "Multiline via \\n.", - "minLength": 1, - "type": "string" - }, - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "kind", - "text", - "x", - "y", - "color" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "kind": { - "const": "grid", - "type": "string" - }, - "legend": { - "additionalProperties": { - "anyOf": [ - { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - { - "type": "null" - } - ], - "description": "Colour as #rrggbb or #rrggbbaa." - }, - "description": "One character → colour; null is transparent. '.' is transparent unless you redefine it.", - "type": "object" - }, - "rows": { - "description": "Top to bottom, one character per pixel, every row the same width.", - "items": { - "minLength": 1, - "type": "string" - }, - "maxItems": 256, - "minItems": 1, - "type": "array" - }, - "transparent": { - "default": "erase", - "description": "Transparent cells: 'erase' clears them, so the grid's rectangle ends up exactly as written; 'skip' leaves the pixel underneath, to stamp a shape over existing art.", - "enum": [ - "erase", - "skip" - ], - "type": "string" - }, - "x": { - "default": 0, - "description": "Sprite x of the grid's left column.", - "type": "integer" - }, - "y": { - "default": 0, - "description": "Sprite y of the grid's top row.", - "type": "integer" - } - }, - "required": [ - "kind", - "legend", - "rows" - ], - "type": "object" - } -]New value: +[ + { + "additionalProperties": false, + "properties": { + "color": { + "description": "Colour as #rrggbb or #rrggbbaa.", + "pattern": "^#?([0-9a-fA-F]{6}|[0-9a-fA-F]{8})$", + "type": "string" + }, + "kind": { + "const": "pixels", + "type": "string" + }, + "points": { + "items": { + "additionalProperties": false, + "properties": { + "color": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color", + "description": "Per-pixel colour. Falls back to the op's `color`." + }, + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + }, + "maxItems": 20000, + "minItems": 1, + "type": "array" + } + }, + "required": [ + "kind", + "points" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "color": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "from": { + "additionalProperties": false, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + }, + "kind": { + "const": "line", + "type": "string" + }, + "thickness": { + "default": 1, + "exclusiveMinimum": 0, + "maximum": 64, + "type": "integer" + }, + "to": { + "additionalProperties": false, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + } + }, + "required": [ + "kind", + "color", + "from", + "to" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "closed": { + "default": false, + "type": "boolean" + }, + "color": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "fill": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color", + "description": "Fill colour; only meaningful when closed." + }, + "kind": { + "const": "polyline", + "type": "string" + }, + "points": { + "items": { + "additionalProperties": false, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + }, + "minItems": 2, + "type": "array" + } + }, + "required": [ + "kind", + "color", + "points" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "color": { + "description": "Outline colour.", + "pattern": "^#?([0-9a-fA-F]{6}|[0-9a-fA-F]{8})$", + "type": "string" + }, + "fill": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color", + "description": "Omit for an outline only." + }, + "kind": { + "const": "rect", + "type": "string" + }, + "rect": { + "additionalProperties": false, + "properties": { + "height": { + "exclusiveMinimum": 0, + "type": "integer" + }, + "width": { + "exclusiveMinimum": 0, + "type": "integer" + }, + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y", + "width", + "height" + ], + "type": "object" + } + }, + "required": [ + "kind", + "color", + "rect" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "color": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "fill": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color", + "description": "Colour as #rrggbb or #rrggbbaa." + }, + "kind": { + "const": "ellipse", + "type": "string" + }, + "rect": { + "additionalProperties": false, + "description": "Bounding box of the ellipse.", + "properties": { + "height": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/height" + }, + "width": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/width" + }, + "x": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/x" + }, + "y": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/y" + } + }, + "required": [ + "x", + "y", + "width", + "height" + ], + "type": "object" + } + }, + "required": [ + "kind", + "color", + "rect" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "at": { + "additionalProperties": false, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + }, + "color": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "contiguous": { + "default": true, + "type": "boolean" + }, + "kind": { + "const": "fill", + "type": "string" + }, + "tolerance": { + "default": 0, + "description": "Largest per-channel difference (0–255) still counted as the clicked colour. RGB sprites only; indexed and grayscale fills stay exact.", + "maximum": 255, + "minimum": 0, + "type": "integer" + } + }, + "required": [ + "kind", + "color", + "at" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "from": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "kind": { + "const": "replace", + "type": "string" + }, + "region": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect" + }, + "to": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + } + }, + "required": [ + "kind", + "from", + "to" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "colorA": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "colorB": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "kind": { + "const": "dither", + "type": "string" + }, + "pattern": { + "default": "bayer4", + "enum": [ + "checker", + "bayer2", + "bayer4", + "bayer8", + "noise" + ], + "type": "string" + }, + "ratio": { + "default": 0.5, + "description": "0 = all colorA, 1 = all colorB.", + "maximum": 1, + "minimum": 0, + "type": "number" + }, + "rect": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect" + } + }, + "required": [ + "kind", + "rect", + "colorA", + "colorB" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "direction": { + "default": "vertical", + "enum": [ + "vertical", + "horizontal", + "diagonal", + "radial" + ], + "type": "string" + }, + "dither": { + "default": false, + "description": "Dither the band boundaries.", + "type": "boolean" + }, + "from": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "kind": { + "const": "gradient", + "type": "string" + }, + "rect": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect" + }, + "steps": { + "default": 4, + "description": "Banded, not smooth — a smooth gradient is not pixel art.", + "maximum": 64, + "minimum": 2, + "type": "integer" + }, + "to": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + } + }, + "required": [ + "kind", + "rect", + "from", + "to" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "kind": { + "const": "clear", + "type": "string" + }, + "region": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect", + "description": "Omit to clear the whole cel." + } + }, + "required": [ + "kind" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "flipHorizontal": { + "default": false, + "type": "boolean" + }, + "flipVertical": { + "default": false, + "type": "boolean" + }, + "from": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect" + }, + "fromFrame": { + "exclusiveMinimum": 0, + "type": "integer" + }, + "fromLayer": { + "type": "string" + }, + "kind": { + "const": "blit", + "type": "string" + }, + "skipTransparent": { + "default": true, + "type": "boolean" + }, + "to": { + "additionalProperties": false, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + } + }, + "required": [ + "kind", + "from", + "to" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "anchor": { + "default": "top_left", + "description": "Resolved against the glyph ink box, not the full advance box — outline and shadow never shift it.", + "enum": [ + "top_left", + "top", + "top_right", + "left", + "center", + "right", + "bottom_left", + "bottom", + "bottom_right", + "baseline_left", + "baseline", + "baseline_right" + ], + "type": "string" + }, + "bold": { + "default": 0, + "description": "Grid-cell passes grown rightward; 0 is regular weight.", + "maximum": 3, + "minimum": 0, + "type": "integer" + }, + "color": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "font": { + "default": "pixel5x7", + "description": "Name in knowledge/fonts, without the .json extension.", + "type": "string" + }, + "kind": { + "const": "text", + "type": "string" + }, + "letterSpacing": { + "default": 1, + "type": "integer" + }, + "lineSpacing": { + "default": 1, + "type": "integer" + }, + "outlineColor": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color", + "description": "Colour as #rrggbb or #rrggbbaa." + }, + "outlineDiagonals": { + "default": true, + "description": "8-neighbour outline instead of 4.", + "type": "boolean" + }, + "scale": { + "default": 1, + "maximum": 8, + "minimum": 1, + "type": "integer" + }, + "shadowColor": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color", + "description": "Colour as #rrggbb or #rrggbbaa." + }, + "shadowOffset": { + "additionalProperties": false, + "default": { + "x": 1, + "y": 1 + }, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + }, + "text": { + "description": "Multiline via \\n.", + "minLength": 1, + "type": "string" + }, + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "kind", + "text", + "x", + "y", + "color" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "kind": { + "const": "grid", + "type": "string" + }, + "legend": { + "additionalProperties": { + "anyOf": [ + { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + { + "type": "null" + } + ], + "description": "Colour as #rrggbb or #rrggbbaa." + }, + "description": "One character → colour; null is transparent. '.' is transparent unless you redefine it.", + "type": "object" + }, + "rows": { + "description": "Top to bottom, one character per pixel, every row the same width. Up to the canvas size.", + "items": { + "minLength": 1, + "type": "string" + }, + "minItems": 1, + "type": "array" + }, + "transparent": { + "default": "erase", + "description": "Transparent cells: 'erase' clears them, so the grid's rectangle ends up exactly as written; 'skip' leaves the pixel underneath, to stamp a shape over existing art.", + "enum": [ + "erase", + "skip" + ], + "type": "string" + }, + "x": { + "default": 0, + "description": "Sprite x of the grid's left column.", + "type": "integer" + }, + "y": { + "default": 0, + "description": "Sprite y of the grid's top row.", + "type": "integer" + } + }, + "required": [ + "kind", + "legend", + "rows" + ], + "type": "object" + } +]
- Changed
look3 fields changed- changed
Input schema / properties / region / descriptionPrevious value: -"Crop. Required for 'ascii' on sprites larger than 64×64."New value: +"Crop. Omit to read the whole canvas." - changed
Output schema / properties / legend / descriptionPrevious value: -"glyph → #rrggbb."New value: +"glyph → #rrggbb. Palette colours keep the same glyph across every read of the sprite." - added
Output schema / properties / offPaletteAdded value: +{ + "description": "ascii/diff: glyphs whose colour is not in the palette. Their assignment can change between reads — do not reuse them across regions.", + "items": { + "type": "string" + }, + "type": "array" +}
5 tool updates
v0.5.0- Changed
draw1 field changed- changed
Input schema / properties / ops / items / anyOfPrevious value: -[ - { - "additionalProperties": false, - "properties": { - "color": { - "description": "Colour as #rrggbb or #rrggbbaa.", - "pattern": "^#?([0-9a-fA-F]{6}|[0-9a-fA-F]{8})$", - "type": "string" - }, - "kind": { - "const": "pixels", - "type": "string" - }, - "points": { - "items": { - "additionalProperties": false, - "properties": { - "color": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color", - "description": "Per-pixel colour. Falls back to the op's `color`." - }, - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - }, - "maxItems": 20000, - "minItems": 1, - "type": "array" - } - }, - "required": [ - "kind", - "points" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "color": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "from": { - "additionalProperties": false, - "properties": { - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - }, - "kind": { - "const": "line", - "type": "string" - }, - "thickness": { - "default": 1, - "exclusiveMinimum": 0, - "maximum": 64, - "type": "integer" - }, - "to": { - "additionalProperties": false, - "properties": { - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - } - }, - "required": [ - "kind", - "color", - "from", - "to" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "closed": { - "default": false, - "type": "boolean" - }, - "color": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "fill": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color", - "description": "Fill colour; only meaningful when closed." - }, - "kind": { - "const": "polyline", - "type": "string" - }, - "points": { - "items": { - "additionalProperties": false, - "properties": { - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - }, - "minItems": 2, - "type": "array" - } - }, - "required": [ - "kind", - "color", - "points" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "color": { - "description": "Outline colour.", - "pattern": "^#?([0-9a-fA-F]{6}|[0-9a-fA-F]{8})$", - "type": "string" - }, - "fill": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color", - "description": "Omit for an outline only." - }, - "kind": { - "const": "rect", - "type": "string" - }, - "rect": { - "additionalProperties": false, - "properties": { - "height": { - "exclusiveMinimum": 0, - "type": "integer" - }, - "width": { - "exclusiveMinimum": 0, - "type": "integer" - }, - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y", - "width", - "height" - ], - "type": "object" - } - }, - "required": [ - "kind", - "color", - "rect" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "color": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "fill": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color", - "description": "Colour as #rrggbb or #rrggbbaa." - }, - "kind": { - "const": "ellipse", - "type": "string" - }, - "rect": { - "additionalProperties": false, - "description": "Bounding box of the ellipse.", - "properties": { - "height": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/height" - }, - "width": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/width" - }, - "x": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/x" - }, - "y": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/y" - } - }, - "required": [ - "x", - "y", - "width", - "height" - ], - "type": "object" - } - }, - "required": [ - "kind", - "color", - "rect" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "at": { - "additionalProperties": false, - "properties": { - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - }, - "color": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "contiguous": { - "default": true, - "type": "boolean" - }, - "kind": { - "const": "fill", - "type": "string" - }, - "tolerance": { - "default": 0, - "maximum": 255, - "minimum": 0, - "type": "integer" - } - }, - "required": [ - "kind", - "color", - "at" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "from": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "kind": { - "const": "replace", - "type": "string" - }, - "region": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect" - }, - "to": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - } - }, - "required": [ - "kind", - "from", - "to" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "colorA": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "colorB": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "kind": { - "const": "dither", - "type": "string" - }, - "pattern": { - "default": "bayer4", - "enum": [ - "checker", - "bayer2", - "bayer4", - "bayer8", - "noise" - ], - "type": "string" - }, - "ratio": { - "default": 0.5, - "description": "0 = all colorA, 1 = all colorB.", - "maximum": 1, - "minimum": 0, - "type": "number" - }, - "rect": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect" - } - }, - "required": [ - "kind", - "rect", - "colorA", - "colorB" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "direction": { - "default": "vertical", - "enum": [ - "vertical", - "horizontal", - "diagonal", - "radial" - ], - "type": "string" - }, - "dither": { - "default": false, - "description": "Dither the band boundaries.", - "type": "boolean" - }, - "from": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "kind": { - "const": "gradient", - "type": "string" - }, - "rect": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect" - }, - "steps": { - "default": 4, - "description": "Banded, not smooth — a smooth gradient is not pixel art.", - "maximum": 64, - "minimum": 2, - "type": "integer" - }, - "to": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - } - }, - "required": [ - "kind", - "rect", - "from", - "to" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "kind": { - "const": "clear", - "type": "string" - }, - "region": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect", - "description": "Omit to clear the whole cel." - } - }, - "required": [ - "kind" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "flipHorizontal": { - "default": false, - "type": "boolean" - }, - "flipVertical": { - "default": false, - "type": "boolean" - }, - "from": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect" - }, - "fromFrame": { - "exclusiveMinimum": 0, - "type": "integer" - }, - "fromLayer": { - "type": "string" - }, - "kind": { - "const": "blit", - "type": "string" - }, - "skipTransparent": { - "default": true, - "type": "boolean" - }, - "to": { - "additionalProperties": false, - "properties": { - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - } - }, - "required": [ - "kind", - "from", - "to" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "anchor": { - "default": "top_left", - "description": "Resolved against the glyph ink box, not the full advance box — outline and shadow never shift it.", - "enum": [ - "top_left", - "top", - "top_right", - "left", - "center", - "right", - "bottom_left", - "bottom", - "bottom_right", - "baseline_left", - "baseline", - "baseline_right" - ], - "type": "string" - }, - "bold": { - "default": 0, - "description": "Grid-cell passes grown rightward; 0 is regular weight.", - "maximum": 3, - "minimum": 0, - "type": "integer" - }, - "color": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "font": { - "default": "pixel5x7", - "description": "Name in knowledge/fonts, without the .json extension.", - "type": "string" - }, - "kind": { - "const": "text", - "type": "string" - }, - "letterSpacing": { - "default": 1, - "type": "integer" - }, - "lineSpacing": { - "default": 1, - "type": "integer" - }, - "outlineColor": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color", - "description": "Colour as #rrggbb or #rrggbbaa." - }, - "outlineDiagonals": { - "default": true, - "description": "8-neighbour outline instead of 4.", - "type": "boolean" - }, - "scale": { - "default": 1, - "maximum": 8, - "minimum": 1, - "type": "integer" - }, - "shadowColor": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color", - "description": "Colour as #rrggbb or #rrggbbaa." - }, - "shadowOffset": { - "additionalProperties": false, - "default": { - "x": 1, - "y": 1 - }, - "properties": { - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - }, - "text": { - "description": "Multiline via \\n.", - "minLength": 1, - "type": "string" - }, - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "kind", - "text", - "x", - "y", - "color" - ], - "type": "object" - } -]New value: +[ + { + "additionalProperties": false, + "properties": { + "color": { + "description": "Colour as #rrggbb or #rrggbbaa.", + "pattern": "^#?([0-9a-fA-F]{6}|[0-9a-fA-F]{8})$", + "type": "string" + }, + "kind": { + "const": "pixels", + "type": "string" + }, + "points": { + "items": { + "additionalProperties": false, + "properties": { + "color": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color", + "description": "Per-pixel colour. Falls back to the op's `color`." + }, + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + }, + "maxItems": 20000, + "minItems": 1, + "type": "array" + } + }, + "required": [ + "kind", + "points" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "color": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "from": { + "additionalProperties": false, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + }, + "kind": { + "const": "line", + "type": "string" + }, + "thickness": { + "default": 1, + "exclusiveMinimum": 0, + "maximum": 64, + "type": "integer" + }, + "to": { + "additionalProperties": false, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + } + }, + "required": [ + "kind", + "color", + "from", + "to" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "closed": { + "default": false, + "type": "boolean" + }, + "color": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "fill": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color", + "description": "Fill colour; only meaningful when closed." + }, + "kind": { + "const": "polyline", + "type": "string" + }, + "points": { + "items": { + "additionalProperties": false, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + }, + "minItems": 2, + "type": "array" + } + }, + "required": [ + "kind", + "color", + "points" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "color": { + "description": "Outline colour.", + "pattern": "^#?([0-9a-fA-F]{6}|[0-9a-fA-F]{8})$", + "type": "string" + }, + "fill": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color", + "description": "Omit for an outline only." + }, + "kind": { + "const": "rect", + "type": "string" + }, + "rect": { + "additionalProperties": false, + "properties": { + "height": { + "exclusiveMinimum": 0, + "type": "integer" + }, + "width": { + "exclusiveMinimum": 0, + "type": "integer" + }, + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y", + "width", + "height" + ], + "type": "object" + } + }, + "required": [ + "kind", + "color", + "rect" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "color": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "fill": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color", + "description": "Colour as #rrggbb or #rrggbbaa." + }, + "kind": { + "const": "ellipse", + "type": "string" + }, + "rect": { + "additionalProperties": false, + "description": "Bounding box of the ellipse.", + "properties": { + "height": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/height" + }, + "width": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/width" + }, + "x": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/x" + }, + "y": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/y" + } + }, + "required": [ + "x", + "y", + "width", + "height" + ], + "type": "object" + } + }, + "required": [ + "kind", + "color", + "rect" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "at": { + "additionalProperties": false, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + }, + "color": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "contiguous": { + "default": true, + "type": "boolean" + }, + "kind": { + "const": "fill", + "type": "string" + }, + "tolerance": { + "default": 0, + "description": "Largest per-channel difference (0–255) still counted as the clicked colour. RGB sprites only; indexed and grayscale fills stay exact.", + "maximum": 255, + "minimum": 0, + "type": "integer" + } + }, + "required": [ + "kind", + "color", + "at" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "from": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "kind": { + "const": "replace", + "type": "string" + }, + "region": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect" + }, + "to": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + } + }, + "required": [ + "kind", + "from", + "to" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "colorA": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "colorB": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "kind": { + "const": "dither", + "type": "string" + }, + "pattern": { + "default": "bayer4", + "enum": [ + "checker", + "bayer2", + "bayer4", + "bayer8", + "noise" + ], + "type": "string" + }, + "ratio": { + "default": 0.5, + "description": "0 = all colorA, 1 = all colorB.", + "maximum": 1, + "minimum": 0, + "type": "number" + }, + "rect": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect" + } + }, + "required": [ + "kind", + "rect", + "colorA", + "colorB" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "direction": { + "default": "vertical", + "enum": [ + "vertical", + "horizontal", + "diagonal", + "radial" + ], + "type": "string" + }, + "dither": { + "default": false, + "description": "Dither the band boundaries.", + "type": "boolean" + }, + "from": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "kind": { + "const": "gradient", + "type": "string" + }, + "rect": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect" + }, + "steps": { + "default": 4, + "description": "Banded, not smooth — a smooth gradient is not pixel art.", + "maximum": 64, + "minimum": 2, + "type": "integer" + }, + "to": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + } + }, + "required": [ + "kind", + "rect", + "from", + "to" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "kind": { + "const": "clear", + "type": "string" + }, + "region": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect", + "description": "Omit to clear the whole cel." + } + }, + "required": [ + "kind" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "flipHorizontal": { + "default": false, + "type": "boolean" + }, + "flipVertical": { + "default": false, + "type": "boolean" + }, + "from": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect" + }, + "fromFrame": { + "exclusiveMinimum": 0, + "type": "integer" + }, + "fromLayer": { + "type": "string" + }, + "kind": { + "const": "blit", + "type": "string" + }, + "skipTransparent": { + "default": true, + "type": "boolean" + }, + "to": { + "additionalProperties": false, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + } + }, + "required": [ + "kind", + "from", + "to" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "anchor": { + "default": "top_left", + "description": "Resolved against the glyph ink box, not the full advance box — outline and shadow never shift it.", + "enum": [ + "top_left", + "top", + "top_right", + "left", + "center", + "right", + "bottom_left", + "bottom", + "bottom_right", + "baseline_left", + "baseline", + "baseline_right" + ], + "type": "string" + }, + "bold": { + "default": 0, + "description": "Grid-cell passes grown rightward; 0 is regular weight.", + "maximum": 3, + "minimum": 0, + "type": "integer" + }, + "color": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "font": { + "default": "pixel5x7", + "description": "Name in knowledge/fonts, without the .json extension.", + "type": "string" + }, + "kind": { + "const": "text", + "type": "string" + }, + "letterSpacing": { + "default": 1, + "type": "integer" + }, + "lineSpacing": { + "default": 1, + "type": "integer" + }, + "outlineColor": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color", + "description": "Colour as #rrggbb or #rrggbbaa." + }, + "outlineDiagonals": { + "default": true, + "description": "8-neighbour outline instead of 4.", + "type": "boolean" + }, + "scale": { + "default": 1, + "maximum": 8, + "minimum": 1, + "type": "integer" + }, + "shadowColor": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color", + "description": "Colour as #rrggbb or #rrggbbaa." + }, + "shadowOffset": { + "additionalProperties": false, + "default": { + "x": 1, + "y": 1 + }, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + }, + "text": { + "description": "Multiline via \\n.", + "minLength": 1, + "type": "string" + }, + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "kind", + "text", + "x", + "y", + "color" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "kind": { + "const": "grid", + "type": "string" + }, + "legend": { + "additionalProperties": { + "anyOf": [ + { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + { + "type": "null" + } + ], + "description": "Colour as #rrggbb or #rrggbbaa." + }, + "description": "One character → colour; null is transparent. '.' is transparent unless you redefine it.", + "type": "object" + }, + "rows": { + "description": "Top to bottom, one character per pixel, every row the same width.", + "items": { + "minLength": 1, + "type": "string" + }, + "maxItems": 256, + "minItems": 1, + "type": "array" + }, + "transparent": { + "default": "erase", + "description": "Transparent cells: 'erase' clears them, so the grid's rectangle ends up exactly as written; 'skip' leaves the pixel underneath, to stamp a shape over existing art.", + "enum": [ + "erase", + "skip" + ], + "type": "string" + }, + "x": { + "default": 0, + "description": "Sprite x of the grid's left column.", + "type": "integer" + }, + "y": { + "default": 0, + "description": "Sprite y of the grid's top row.", + "type": "integer" + } + }, + "required": [ + "kind", + "legend", + "rows" + ], + "type": "object" + } +]
- Changed
export2 fields changed- changed
Input schema / properties / layers / descriptionPrevious value: -"Export only these layers."New value: +"Export only these layers (names or group paths; a group brings its children). png, gif, frames, spritesheet; 'aseprite' refuses it." - changed
Input schema / properties / tags / descriptionPrevious value: -"Export only these tags."New value: +"Export only the frames these tags cover. gif, frames, spritesheet; 'png' and 'aseprite' refuse it. An unknown tag is refused."
- Changed
frame1 field changed- changed
Input schema / properties / toIndex / descriptionPrevious value: -"For 'reorder'."New value: +"For 'reorder': the 1-based position `frame` ends up at. Its cels and duration move with it; tag ranges stay where they are."
- Changed
look4 fields changed- changed
Input schema / properties / layer / descriptionPrevious value: -"Read a single layer instead of the composited image."New value: +"Read a single layer instead of the composited image. Honoured by preview, ascii, diff, filmstrip and onion; compare has its own `reference`." - added
Input schema / properties / rulersAdded value: +{ + "default": true, + "description": "ascii: false drops the coordinate rulers and row labels, leaving rows you can edit and pass straight to `draw` kind 'grid' with the reported origin.", + "type": "boolean" +} - added
Output schema / properties / gridRowsAdded value: +{ + "description": "ascii: the bare rows, '.' transparent — `draw` kind 'grid' `rows`, with `legend` and `origin`.", + "items": { + "type": "string" + }, + "type": "array" +} - added
Output schema / properties / originAdded value: +{ + "additionalProperties": false, + "description": "ascii: sprite position of the grid's top-left cell — the `x`/`y` for `draw` kind 'grid'.", + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" +}
- Changed
select1 field changed- added
Input schema / properties / tolerance / descriptionAdded value: +"Largest per-channel difference (0–255) still counted as the clicked colour. RGB sprites only; indexed and grayscale fills stay exact."
11 tool updates
v0.4.0- Changed
cel10 fields changed- added
Input schema / properties / amplitudeXAdded value: +{ + "default": 0, + "description": "For 'oscillate'.", + "type": "integer" +} - added
Input schema / properties / amplitudeYAdded value: +{ + "default": 0, + "description": "For 'oscillate'.", + "type": "integer" +} - added
Input schema / properties / easingAdded value: +{ + "default": "linear", + "description": "For 'tween'.", + "enum": [ + "linear", + "ease_in", + "ease_out", + "ease_in_out", + "smoothstep" + ], + "type": "string" +} - added
Input schema / properties / fromFrameAdded value: +{ + "description": "For 'tween'/'oscillate': the start frame.", + "exclusiveMinimum": 0, + "type": "integer" +} - changed
Input schema / properties / op / enumPrevious value: -[ - "list", - "create", - "clear", - "delete", - "move", - "copy", - "link", - "unlink", - "set" -]New value: +[ + "list", + "create", + "clear", + "delete", + "move", + "copy", + "link", + "unlink", + "set", + "tween", + "oscillate" +] - added
Input schema / properties / periodAdded value: +{ + "description": "For 'oscillate', in frames. Default: the whole fromFrame..toFrame span.", + "minimum": 2, + "type": "integer" +} - added
Input schema / properties / phaseAdded value: +{ + "default": 0, + "description": "For 'oscillate': 0-1 fraction of one period.", + "maximum": 1, + "minimum": 0, + "type": "number" +} - added
Input schema / properties / propertyAdded value: +{ + "description": "For 'tween'.", + "enum": [ + "position", + "opacity" + ], + "type": "string" +} - added
Input schema / properties / toAdded value: +{ + "anyOf": [ + { + "additionalProperties": false, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + }, + { + "maximum": 255, + "minimum": 0, + "type": "integer" + } + ], + "description": "For 'tween': end value — {x,y} for property 'position', 0-255 for 'opacity'." +} - added
Output schema / properties / framesAdded value: +{ + "description": "Only present for 'tween' and 'oscillate': one entry per frame touched, ascending.", + "items": { + "additionalProperties": false, + "properties": { + "frame": { + "type": "integer" + }, + "opacity": { + "type": "integer" + }, + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "frame" + ], + "type": "object" + }, + "type": "array" +}
- Changed
draw5 fields changed- added
Input schema / properties / measureOnlyAdded value: +{ + "default": false, + "description": "Every op must be 'text'. Returns each one's ink bounds without calling Aseprite at all — use to size a panel or centre a label before actually drawing it.", + "type": "boolean" +} - changed
Input schema / properties / ops / items / anyOfPrevious value: -[ - { - "additionalProperties": false, - "properties": { - "color": { - "description": "Colour as #rrggbb or #rrggbbaa.", - "pattern": "^#?([0-9a-fA-F]{6}|[0-9a-fA-F]{8})$", - "type": "string" - }, - "kind": { - "const": "pixels", - "type": "string" - }, - "points": { - "items": { - "additionalProperties": false, - "properties": { - "color": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color", - "description": "Per-pixel colour. Falls back to the op's `color`." - }, - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - }, - "maxItems": 20000, - "minItems": 1, - "type": "array" - } - }, - "required": [ - "kind", - "points" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "color": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "from": { - "additionalProperties": false, - "properties": { - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - }, - "kind": { - "const": "line", - "type": "string" - }, - "thickness": { - "default": 1, - "exclusiveMinimum": 0, - "maximum": 64, - "type": "integer" - }, - "to": { - "additionalProperties": false, - "properties": { - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - } - }, - "required": [ - "kind", - "color", - "from", - "to" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "closed": { - "default": false, - "type": "boolean" - }, - "color": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "fill": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color", - "description": "Fill colour; only meaningful when closed." - }, - "kind": { - "const": "polyline", - "type": "string" - }, - "points": { - "items": { - "additionalProperties": false, - "properties": { - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - }, - "minItems": 2, - "type": "array" - } - }, - "required": [ - "kind", - "color", - "points" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "color": { - "description": "Outline colour.", - "pattern": "^#?([0-9a-fA-F]{6}|[0-9a-fA-F]{8})$", - "type": "string" - }, - "fill": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color", - "description": "Omit for an outline only." - }, - "kind": { - "const": "rect", - "type": "string" - }, - "rect": { - "additionalProperties": false, - "properties": { - "height": { - "exclusiveMinimum": 0, - "type": "integer" - }, - "width": { - "exclusiveMinimum": 0, - "type": "integer" - }, - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y", - "width", - "height" - ], - "type": "object" - } - }, - "required": [ - "kind", - "color", - "rect" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "color": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "fill": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color", - "description": "Colour as #rrggbb or #rrggbbaa." - }, - "kind": { - "const": "ellipse", - "type": "string" - }, - "rect": { - "additionalProperties": false, - "description": "Bounding box of the ellipse.", - "properties": { - "height": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/height" - }, - "width": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/width" - }, - "x": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/x" - }, - "y": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/y" - } - }, - "required": [ - "x", - "y", - "width", - "height" - ], - "type": "object" - } - }, - "required": [ - "kind", - "color", - "rect" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "at": { - "additionalProperties": false, - "properties": { - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - }, - "color": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "contiguous": { - "default": true, - "type": "boolean" - }, - "kind": { - "const": "fill", - "type": "string" - }, - "tolerance": { - "default": 0, - "maximum": 255, - "minimum": 0, - "type": "integer" - } - }, - "required": [ - "kind", - "color", - "at" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "from": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "kind": { - "const": "replace", - "type": "string" - }, - "region": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect" - }, - "to": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - } - }, - "required": [ - "kind", - "from", - "to" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "colorA": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "colorB": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "kind": { - "const": "dither", - "type": "string" - }, - "pattern": { - "default": "bayer4", - "enum": [ - "checker", - "bayer2", - "bayer4", - "bayer8", - "noise" - ], - "type": "string" - }, - "ratio": { - "default": 0.5, - "description": "0 = all colorA, 1 = all colorB.", - "maximum": 1, - "minimum": 0, - "type": "number" - }, - "rect": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect" - } - }, - "required": [ - "kind", - "rect", - "colorA", - "colorB" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "direction": { - "default": "vertical", - "enum": [ - "vertical", - "horizontal", - "diagonal", - "radial" - ], - "type": "string" - }, - "dither": { - "default": false, - "description": "Dither the band boundaries.", - "type": "boolean" - }, - "from": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - }, - "kind": { - "const": "gradient", - "type": "string" - }, - "rect": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect" - }, - "steps": { - "default": 4, - "description": "Banded, not smooth — a smooth gradient is not pixel art.", - "maximum": 64, - "minimum": 2, - "type": "integer" - }, - "to": { - "$ref": "#/properties/ops/items/anyOf/0/properties/color" - } - }, - "required": [ - "kind", - "rect", - "from", - "to" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "kind": { - "const": "clear", - "type": "string" - }, - "region": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect", - "description": "Omit to clear the whole cel." - } - }, - "required": [ - "kind" - ], - "type": "object" - }, - { - "additionalProperties": false, - "properties": { - "flipHorizontal": { - "default": false, - "type": "boolean" - }, - "flipVertical": { - "default": false, - "type": "boolean" - }, - "from": { - "$ref": "#/properties/ops/items/anyOf/3/properties/rect" - }, - "fromFrame": { - "exclusiveMinimum": 0, - "type": "integer" - }, - "fromLayer": { - "type": "string" - }, - "kind": { - "const": "blit", - "type": "string" - }, - "skipTransparent": { - "default": true, - "type": "boolean" - }, - "to": { - "additionalProperties": false, - "properties": { - "x": { - "type": "integer" - }, - "y": { - "type": "integer" - } - }, - "required": [ - "x", - "y" - ], - "type": "object" - } - }, - "required": [ - "kind", - "from", - "to" - ], - "type": "object" - } -]New value: +[ + { + "additionalProperties": false, + "properties": { + "color": { + "description": "Colour as #rrggbb or #rrggbbaa.", + "pattern": "^#?([0-9a-fA-F]{6}|[0-9a-fA-F]{8})$", + "type": "string" + }, + "kind": { + "const": "pixels", + "type": "string" + }, + "points": { + "items": { + "additionalProperties": false, + "properties": { + "color": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color", + "description": "Per-pixel colour. Falls back to the op's `color`." + }, + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + }, + "maxItems": 20000, + "minItems": 1, + "type": "array" + } + }, + "required": [ + "kind", + "points" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "color": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "from": { + "additionalProperties": false, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + }, + "kind": { + "const": "line", + "type": "string" + }, + "thickness": { + "default": 1, + "exclusiveMinimum": 0, + "maximum": 64, + "type": "integer" + }, + "to": { + "additionalProperties": false, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + } + }, + "required": [ + "kind", + "color", + "from", + "to" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "closed": { + "default": false, + "type": "boolean" + }, + "color": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "fill": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color", + "description": "Fill colour; only meaningful when closed." + }, + "kind": { + "const": "polyline", + "type": "string" + }, + "points": { + "items": { + "additionalProperties": false, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + }, + "minItems": 2, + "type": "array" + } + }, + "required": [ + "kind", + "color", + "points" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "color": { + "description": "Outline colour.", + "pattern": "^#?([0-9a-fA-F]{6}|[0-9a-fA-F]{8})$", + "type": "string" + }, + "fill": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color", + "description": "Omit for an outline only." + }, + "kind": { + "const": "rect", + "type": "string" + }, + "rect": { + "additionalProperties": false, + "properties": { + "height": { + "exclusiveMinimum": 0, + "type": "integer" + }, + "width": { + "exclusiveMinimum": 0, + "type": "integer" + }, + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y", + "width", + "height" + ], + "type": "object" + } + }, + "required": [ + "kind", + "color", + "rect" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "color": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "fill": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color", + "description": "Colour as #rrggbb or #rrggbbaa." + }, + "kind": { + "const": "ellipse", + "type": "string" + }, + "rect": { + "additionalProperties": false, + "description": "Bounding box of the ellipse.", + "properties": { + "height": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/height" + }, + "width": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/width" + }, + "x": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/x" + }, + "y": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect/properties/y" + } + }, + "required": [ + "x", + "y", + "width", + "height" + ], + "type": "object" + } + }, + "required": [ + "kind", + "color", + "rect" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "at": { + "additionalProperties": false, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + }, + "color": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "contiguous": { + "default": true, + "type": "boolean" + }, + "kind": { + "const": "fill", + "type": "string" + }, + "tolerance": { + "default": 0, + "maximum": 255, + "minimum": 0, + "type": "integer" + } + }, + "required": [ + "kind", + "color", + "at" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "from": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "kind": { + "const": "replace", + "type": "string" + }, + "region": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect" + }, + "to": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + } + }, + "required": [ + "kind", + "from", + "to" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "colorA": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "colorB": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "kind": { + "const": "dither", + "type": "string" + }, + "pattern": { + "default": "bayer4", + "enum": [ + "checker", + "bayer2", + "bayer4", + "bayer8", + "noise" + ], + "type": "string" + }, + "ratio": { + "default": 0.5, + "description": "0 = all colorA, 1 = all colorB.", + "maximum": 1, + "minimum": 0, + "type": "number" + }, + "rect": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect" + } + }, + "required": [ + "kind", + "rect", + "colorA", + "colorB" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "direction": { + "default": "vertical", + "enum": [ + "vertical", + "horizontal", + "diagonal", + "radial" + ], + "type": "string" + }, + "dither": { + "default": false, + "description": "Dither the band boundaries.", + "type": "boolean" + }, + "from": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "kind": { + "const": "gradient", + "type": "string" + }, + "rect": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect" + }, + "steps": { + "default": 4, + "description": "Banded, not smooth — a smooth gradient is not pixel art.", + "maximum": 64, + "minimum": 2, + "type": "integer" + }, + "to": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + } + }, + "required": [ + "kind", + "rect", + "from", + "to" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "kind": { + "const": "clear", + "type": "string" + }, + "region": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect", + "description": "Omit to clear the whole cel." + } + }, + "required": [ + "kind" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "flipHorizontal": { + "default": false, + "type": "boolean" + }, + "flipVertical": { + "default": false, + "type": "boolean" + }, + "from": { + "$ref": "#/properties/ops/items/anyOf/3/properties/rect" + }, + "fromFrame": { + "exclusiveMinimum": 0, + "type": "integer" + }, + "fromLayer": { + "type": "string" + }, + "kind": { + "const": "blit", + "type": "string" + }, + "skipTransparent": { + "default": true, + "type": "boolean" + }, + "to": { + "additionalProperties": false, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + } + }, + "required": [ + "kind", + "from", + "to" + ], + "type": "object" + }, + { + "additionalProperties": false, + "properties": { + "anchor": { + "default": "top_left", + "description": "Resolved against the glyph ink box, not the full advance box — outline and shadow never shift it.", + "enum": [ + "top_left", + "top", + "top_right", + "left", + "center", + "right", + "bottom_left", + "bottom", + "bottom_right", + "baseline_left", + "baseline", + "baseline_right" + ], + "type": "string" + }, + "bold": { + "default": 0, + "description": "Grid-cell passes grown rightward; 0 is regular weight.", + "maximum": 3, + "minimum": 0, + "type": "integer" + }, + "color": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color" + }, + "font": { + "default": "pixel5x7", + "description": "Name in knowledge/fonts, without the .json extension.", + "type": "string" + }, + "kind": { + "const": "text", + "type": "string" + }, + "letterSpacing": { + "default": 1, + "type": "integer" + }, + "lineSpacing": { + "default": 1, + "type": "integer" + }, + "outlineColor": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color", + "description": "Colour as #rrggbb or #rrggbbaa." + }, + "outlineDiagonals": { + "default": true, + "description": "8-neighbour outline instead of 4.", + "type": "boolean" + }, + "scale": { + "default": 1, + "maximum": 8, + "minimum": 1, + "type": "integer" + }, + "shadowColor": { + "$ref": "#/properties/ops/items/anyOf/0/properties/color", + "description": "Colour as #rrggbb or #rrggbbaa." + }, + "shadowOffset": { + "additionalProperties": false, + "default": { + "x": 1, + "y": 1 + }, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + }, + "text": { + "description": "Multiline via \\n.", + "minLength": 1, + "type": "string" + }, + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "kind", + "text", + "x", + "y", + "color" + ], + "type": "object" + } +] - added
Output schema / properties / measureOnlyAdded value: +{ + "type": "boolean" +} - added
Output schema / properties / textBoundsAdded value: +{ + "description": "Only present when `measureOnly` was set.", + "items": { + "additionalProperties": false, + "properties": { + "bounds": { + "anyOf": [ + { + "additionalProperties": false, + "properties": { + "height": { + "type": "integer" + }, + "width": { + "type": "integer" + }, + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y", + "width", + "height" + ], + "type": "object" + }, + { + "type": "null" + } + ], + "description": "Ink bounds of the laid-out text; null for text with no ink (e.g. all spaces)." + }, + "index": { + "description": "Position of this op in the `ops` array.", + "type": "integer" + } + }, + "required": [ + "index" + ], + "type": "object" + }, + "type": "array" +} - removed
Output schema / requiredRemoved value: -[ - "sprite", - "layer", - "frame", - "opsApplied", - "pixelsChanged", - "colorsSnapped" -]
- Changed
layer3 fields changed- added
Input schema / properties / batch / items / properties / toSpriteAdded value: +{ + "description": "For 'duplicate': copy the layer into another OPEN sprite instead of this one.", + "type": "string" +} - added
Input schema / properties / toSpriteAdded value: +{ + "description": "For 'duplicate': copy the layer into another OPEN sprite instead of this one.", + "type": "string" +} - added
Output schema / properties / duplicatedAdded value: +{ + "description": "Present when a 'duplicate' op in this call used `toSprite`.", + "items": { + "additionalProperties": false, + "properties": { + "framesDropped": { + "description": "Cels whose frame index exceeded the target's frame count.", + "type": "integer" + }, + "name": { + "description": "Name it got in the target sprite; suffixed on a name clash.", + "type": "string" + }, + "sourceLayer": { + "type": "string" + }, + "toSprite": { + "description": "Target as '#<id>' — stable even when several documents share a name.", + "type": "string" + } + }, + "required": [ + "sourceLayer", + "name", + "toSprite", + "framesDropped" + ], + "type": "object" + }, + "type": "array" +}
- Changed
look9 fields changed- added
Input schema / properties / framesAfterAdded value: +{ + "default": 1, + "description": "Onion: ghost frames after the target.", + "maximum": 8, + "minimum": 0, + "type": "integer" +} - added
Input schema / properties / framesBeforeAdded value: +{ + "default": 1, + "description": "Onion: ghost frames before the target.", + "maximum": 8, + "minimum": 0, + "type": "integer" +} - added
Input schema / properties / ghostOpacityAdded value: +{ + "default": 90, + "description": "Onion: opacity of the ghosted (non-target) frames.", + "maximum": 255, + "minimum": 0, + "type": "integer" +} - changed
Input schema / properties / op / enumPrevious value: -[ - "preview", - "ascii", - "filmstrip", - "diff" -]New value: +[ + "preview", + "ascii", + "filmstrip", + "diff", + "onion", + "compare" +] - added
Input schema / properties / referenceAdded value: +{ + "description": "Compare: the reference layer. Default 'reference'.", + "type": "string" +} - added
Output schema / properties / changedBoundsAdded value: +{ + "anyOf": [ + { + "additionalProperties": false, + "properties": { + "height": { + "type": "integer" + }, + "width": { + "type": "integer" + }, + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y", + "width", + "height" + ], + "type": "object" + }, + { + "type": "null" + } + ], + "description": "Diff: tight bounding box of every changed pixel. Null when nothing changed." +} - added
Output schema / properties / frames / descriptionAdded value: +"Filmstrip: frame count." - added
Output schema / properties / framesUsedAdded value: +{ + "description": "Onion: 1-based frame numbers composited.", + "items": { + "type": "integer" + }, + "type": "array" +} - added
Output schema / properties / percentChangedAdded value: +{ + "description": "Diff: changed / total * 100.", + "type": "number" +}
- Changed
palette2 fields changed- added
Input schema / properties / maxColorsAdded value: +{ + "default": 16, + "description": "For op 'extract': target palette size.", + "maximum": 256, + "minimum": 2, + "type": "integer" +} - changed
Input schema / properties / op / enumPrevious value: -[ - "get", - "set", - "preset", - "load", - "ramp", - "analyze" -]New value: +[ + "get", + "set", + "preset", + "load", + "ramp", + "analyze", + "extract" +]
- Changed
preflight5 fields changed- added
Input schema / additionalPropertiesAdded value: +false - added
Input schema / properties / modeAdded value: +{ + "description": "Switch the session to this Aseprite before checking. Omit to keep the current one.", + "enum": [ + "live", + "headless" + ], + "type": "string" +} - added
Output schema / properties / modeAdded value: +{ + "description": "'live' = the user's open window. 'headless' = a batch Aseprite with no window; nothing is on disk until you save or export.", + "enum": [ + "live", + "headless" + ], + "type": "string" +} - added
Output schema / properties / switchedAdded value: +{ + "description": "True when this call changed the session's mode.", + "type": "boolean" +} - changed
Output schema / requiredPrevious value: -[ - "ready", - "bridgeConnected", - "pluginConnected", - "features", - "directive" -]New value: +[ + "ready", + "switched", + "mode", + "bridgeConnected", + "pluginConnected", + "features", + "directive" +]
- Changed
reference6 fields changed- changed
Input schema / properties / fit / descriptionPrevious value: -"How to size the image against the canvas."New value: +"How to size the image (or each panel) against the canvas." - added
Input schema / properties / frameAdded value: +{ + "description": "Import: the frame the image — or the first `grid` panel — lands on. Default: the active frame, or frame 1 with `grid`.", + "exclusiveMinimum": 0, + "type": "integer" +} - added
Input schema / properties / gridAdded value: +{ + "additionalProperties": false, + "description": "Import a storyboard: split the (cropped) source into equal panels and place panel i on frame `frame`+i-1 of one reference layer. The sprite must already have enough frames.", + "properties": { + "columns": { + "exclusiveMinimum": 0, + "type": "integer" + }, + "count": { + "description": "Panels actually used, read row-major. Default: columns × rows.", + "exclusiveMinimum": 0, + "type": "integer" + }, + "gap": { + "default": 0, + "description": "Source pixels between panels.", + "minimum": 0, + "type": "integer" + }, + "rows": { + "exclusiveMinimum": 0, + "type": "integer" + } + }, + "required": [ + "columns", + "rows" + ], + "type": "object" +} - added
Input schema / properties / regionAdded value: +{ + "additionalProperties": false, + "description": "Use only this rectangle of the SOURCE image, in its own pixels — one panel of a concept sheet. Applies to 'import' and 'sample_palette'.", + "properties": { + "height": { + "exclusiveMinimum": 0, + "type": "integer" + }, + "width": { + "exclusiveMinimum": 0, + "type": "integer" + }, + "x": { + "minimum": 0, + "type": "integer" + }, + "y": { + "minimum": 0, + "type": "integer" + } + }, + "required": [ + "x", + "y", + "width", + "height" + ], + "type": "object" +} - added
Output schema / properties / framesAdded value: +{ + "description": "Import: the frames that received a reference cel.", + "items": { + "type": "integer" + }, + "type": "array" +} - added
Output schema / properties / panelsAdded value: +{ + "description": "Import: how many panels were placed.", + "type": "integer" +}
- Changed
sprite_info5 fields changed- changed
Output schema / properties / slices / items / properties / bounds / additionalPropertiesPrevious value: -{ - "type": "number" -}New value: +false - added
Output schema / properties / slices / items / properties / bounds / propertiesAdded value: +{ + "height": { + "exclusiveMinimum": 0, + "type": "integer" + }, + "width": { + "exclusiveMinimum": 0, + "type": "integer" + }, + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } +} - added
Output schema / properties / slices / items / properties / bounds / requiredAdded value: +[ + "x", + "y", + "width", + "height" +] - added
Output schema / properties / slices / items / properties / centerAdded value: +{ + "$ref": "#/properties/slices/items/properties/bounds", + "description": "Nine-slice centre region, relative to the slice. Only when set." +} - added
Output schema / properties / slices / items / properties / pivotAdded value: +{ + "additionalProperties": false, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" +}
- Changed
sprite_manage8 fields changed- added
Input schema / properties / boundsAdded value: +{ + "additionalProperties": false, + "description": "Slice rectangle. Required for 'slice_create'.", + "properties": { + "height": { + "exclusiveMinimum": 0, + "type": "integer" + }, + "width": { + "exclusiveMinimum": 0, + "type": "integer" + }, + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y", + "width", + "height" + ], + "type": "object" +} - added
Input schema / properties / centerAdded value: +{ + "$ref": "#/properties/bounds", + "description": "For slice ops: nine-slice centre region, relative to `bounds`." +} - added
Input schema / properties / colorAdded value: +{ + "description": "For slice ops: slice colour in the timeline, #rrggbb.", + "type": "string" +} - added
Input schema / properties / nameAdded value: +{ + "description": "Slice name. Required for 'slice_create'; identifies it for update/delete.", + "type": "string" +} - changed
Input schema / properties / op / enumPrevious value: -[ - "list", - "new", - "open", - "activate", - "save", - "save_as", - "close", - "resize_canvas", - "set_properties" -]New value: +[ + "list", + "new", + "open", + "activate", + "save", + "save_as", + "close", + "resize_canvas", + "set_properties", + "slice_create", + "slice_update", + "slice_delete" +] - added
Input schema / properties / pivotAdded value: +{ + "additionalProperties": false, + "description": "For slice ops.", + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" +} - added
Output schema / properties / nameAdded value: +{ + "description": "Slice name, for 'slice_delete'.", + "type": "string" +} - added
Output schema / properties / sliceAdded value: +{ + "additionalProperties": false, + "description": "The affected slice, for 'slice_create'/'slice_update'.", + "properties": { + "bounds": { + "additionalProperties": false, + "properties": { + "height": { + "exclusiveMinimum": 0, + "type": "integer" + }, + "width": { + "exclusiveMinimum": 0, + "type": "integer" + }, + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y", + "width", + "height" + ], + "type": "object" + }, + "center": { + "$ref": "#/properties/slice/properties/bounds", + "description": "Nine-slice centre region, relative to the slice. Only when set." + }, + "name": { + "type": "string" + }, + "pivot": { + "additionalProperties": false, + "properties": { + "x": { + "type": "integer" + }, + "y": { + "type": "integer" + } + }, + "required": [ + "x", + "y" + ], + "type": "object" + } + }, + "required": [ + "name", + "bounds" + ], + "type": "object" +}
- Changed
transform2 fields changed- added
Input schema / properties / diagonalsAdded value: +{ + "default": false, + "description": "For 'outline'. Treat diagonal neighbours as touching too (8-neighbour instead of 4).", + "type": "boolean" +} - added
Input schema / properties / sideAdded value: +{ + "default": "outside", + "description": "For 'outline'. 'outside' paints transparent pixels touching opaque ones, growing the cel by one pixel each way. 'inside' recolours opaque pixels that touch transparency instead, same size in and out.", + "enum": [ + "outside", + "inside" + ], + "type": "string" +}
- Changed
validate1 field changed- added
Input schema / properties / expectAdded value: +{ + "additionalProperties": false, + "description": "The animation contract you already know. Runs independently of `checks`, whenever given: flags art outside a layer's expected frame ranges (or a missing cel inside one), and any frame where two named layers' opaque pixels overlap.", + "properties": { + "layerFrames": { + "additionalProperties": { + "items": { + "items": [ + { + "exclusiveMinimum": 0, + "type": "integer" + }, + { + "exclusiveMinimum": 0, + "type": "integer" + } + ], + "maxItems": 2, + "minItems": 2, + "type": "array" + }, + "type": "array" + }, + "description": "Per layer, the [from,to] frame ranges (1-based, inclusive) it should hold ink in.", + "type": "object" + }, + "mustNotOverlap": { + "description": "Layer name pairs whose opaque pixels must never intersect on the same frame.", + "items": { + "items": [ + { + "type": "string" + }, + { + "type": "string" + } + ], + "maxItems": 2, + "minItems": 2, + "type": "array" + }, + "type": "array" + } + }, + "type": "object" +}
17 tool updates
v0.1.6- Changed
cel1 field changed- changed
Input schema / properties / sprite / descriptionPrevious value: -"Sprite filename or id. Omit to use the sprite Aseprite has focused."New value: +"Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused."
- Changed
draw1 field changed- changed
Input schema / properties / sprite / descriptionPrevious value: -"Sprite filename or id. Omit to use the sprite Aseprite has focused."New value: +"Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused."
- Changed
export2 fields changed- changed
Input schema / properties / path / descriptionPrevious value: -"Output file path. For 'frames', a pattern like 'walk_{frame}.png'."New value: +"Output file path. For 'frames', a pattern containing {frame}, e.g. 'walk_{frame}.png' — Aseprite expands it into one file per frame, numbered from 0." - changed
Input schema / properties / sprite / descriptionPrevious value: -"Sprite filename or id. Omit to use the sprite Aseprite has focused."New value: +"Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused."
- Changed
frame1 field changed- changed
Input schema / properties / sprite / descriptionPrevious value: -"Sprite filename or id. Omit to use the sprite Aseprite has focused."New value: +"Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused."
- Changed
layer10 fields changed- changed
Input schema / properties / batch / descriptionPrevious value: -"Array of operation objects, each shaped like the single-op arguments. Applied in order."New value: +"Operations applied in order, in one undoable action. Same shape as the single-op arguments." - changed
Input schema / properties / batch / items / additionalPropertiesPrevious value: -{}New value: +false - added
Input schema / properties / batch / items / propertiesAdded value: +{ + "blendMode": { + "$ref": "#/properties/blendMode" + }, + "editable": { + "type": "boolean" + }, + "index": { + "description": "Target stack position; 0 is bottom.", + "type": "integer" + }, + "name": { + "type": "string" + }, + "names": { + "description": "For 'merge' and bulk 'group'.", + "items": { + "type": "string" + }, + "type": "array" + }, + "newName": { + "type": "string" + }, + "op": { + "$ref": "#/properties/op" + }, + "opacity": { + "maximum": 255, + "minimum": 0, + "type": "integer" + }, + "parent": { + "description": "Group layer to nest under.", + "type": "string" + }, + "visible": { + "type": "boolean" + } +} - added
Input schema / properties / batch / items / requiredAdded value: +[ + "op" +] - added
Input schema / properties / batch / maxItemsAdded value: +128 - changed
Input schema / properties / sprite / descriptionPrevious value: -"Sprite filename or id. Omit to use the sprite Aseprite has focused."New value: +"Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused." - added
Output schema / properties / layers / items / properties / celsAdded value: +{ + "description": "1-based frames that have a cel on this layer.", + "items": { + "type": "integer" + }, + "type": "array" +} - added
Output schema / properties / layers / items / properties / editableAdded value: +{ + "type": "boolean" +} - added
Output schema / properties / layers / items / properties / isTilemapAdded value: +{ + "type": "boolean" +} - changed
Output schema / properties / layers / items / requiredPrevious value: -[ - "name", - "index", - "visible", - "opacity", - "blendMode", - "isGroup" -]New value: +[ + "name", + "index", + "visible", + "editable", + "opacity", + "blendMode", + "isGroup", + "isTilemap", + "cels" +]
- Changed
look3 fields changed- changed
Input schema / properties / scale / descriptionPrevious value: -"Integer upscale for image ops. Omitted means auto."New value: +"Integer upscale for image ops, 1-128 (clamped so the output stays under ~2048px). Omit it — the automatic choice targets a ~1024px long edge, which is what a vision model can actually read." - changed
Input schema / properties / scale / maximumPrevious value: -16New value: +128 - changed
Input schema / properties / sprite / descriptionPrevious value: -"Sprite filename or id. Omit to use the sprite Aseprite has focused."New value: +"Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused."
- Changed
palette2 fields changed- changed
Input schema / properties / sprite / descriptionPrevious value: -"Sprite filename or id. Omit to use the sprite Aseprite has focused."New value: +"Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused." - added
Output schema / properties / pathAdded value: +{ + "description": "Palette file read by op 'load'.", + "type": "string" +}
- Changed
read_pixels1 field changed- changed
Input schema / properties / sprite / descriptionPrevious value: -"Sprite filename or id. Omit to use the sprite Aseprite has focused."New value: +"Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused."
- Changed
recolor1 field changed- changed
Input schema / properties / sprite / descriptionPrevious value: -"Sprite filename or id. Omit to use the sprite Aseprite has focused."New value: +"Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused."
- Changed
reference1 field changed- changed
Input schema / properties / sprite / descriptionPrevious value: -"Sprite filename or id. Omit to use the sprite Aseprite has focused."New value: +"Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused."
- Changed
select1 field changed- changed
Input schema / properties / sprite / descriptionPrevious value: -"Sprite filename or id. Omit to use the sprite Aseprite has focused."New value: +"Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused."
- Changed
sprite_info5 fields changed- changed
Input schema / properties / sprite / descriptionPrevious value: -"Sprite filename or id. Omit to use the sprite Aseprite has focused."New value: +"Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused." - added
Output schema / properties / idAdded value: +{ + "description": "Stable id for this open document. Pass it back as '#<id>'.", + "type": "integer" +} - removed
Output schema / properties / tags / items / properties / repeatRemoved value: -{ - "anyOf": [ - { - "type": "integer" - }, - { - "type": "null" - } - ] -} - added
Output schema / properties / tags / items / properties / repeatsAdded value: +{ + "anyOf": [ + { + "type": "integer" + }, + { + "type": "null" + } + ], + "description": "Loop count; 0 means forever." +} - changed
Output schema / requiredPrevious value: -[ - "name", - "width", - "height", - "colorMode", - "frameCount", - "layers", - "frames", - "tags" -]New value: +[ + "id", + "name", + "width", + "height", + "colorMode", + "frameCount", + "layers", + "frames", + "tags" +]
- Changed
sprite_manage7 fields changed- changed
Input schema / properties / sprite / descriptionPrevious value: -"Sprite filename or id. Omit to use the sprite Aseprite has focused."New value: +"Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused." - added
Output schema / properties / idAdded value: +{ + "description": "Stable id of the affected document; pass it back as '#<id>'.", + "type": "integer" +} - added
Output schema / properties / sprites / items / properties / colorModeAdded value: +{ + "type": "string" +} - added
Output schema / properties / sprites / items / properties / framesAdded value: +{ + "type": "integer" +} - added
Output schema / properties / sprites / items / properties / idAdded value: +{ + "type": "integer" +} - added
Output schema / properties / sprites / items / properties / layersAdded value: +{ + "type": "integer" +} - changed
Output schema / properties / sprites / items / requiredPrevious value: -[ - "name", - "width", - "height", - "active", - "modified" -]New value: +[ + "id", + "name", + "width", + "height", + "colorMode", + "frames", + "layers", + "active", + "modified" +]
- Changed
tag3 fields changed- removed
Input schema / properties / repeatRemoved value: -{ - "description": "0 means loop forever.", - "minimum": 0, - "type": "integer" -} - added
Input schema / properties / repeatsAdded value: +{ + "description": "Loop count; 0 means forever.", + "minimum": 0, + "type": "integer" +} - changed
Input schema / properties / sprite / descriptionPrevious value: -"Sprite filename or id. Omit to use the sprite Aseprite has focused."New value: +"Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused."
- Changed
tileset14 fields changed- changed
Input schema / properties / sprite / descriptionPrevious value: -"Sprite filename or id. Omit to use the sprite Aseprite has focused."New value: +"Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused." - changed
Input schema / properties / tolerance / descriptionPrevious value: -"For 'pack': treat near-identical tiles as one."New value: +"For 'pack': maximum per-channel difference at which two cells count as the same tile. 0 means exact, which is also much faster — anything above 0 compares every cell against every tile found so far." - changed
Input schema / properties / tolerance / maximumPrevious value: -64New value: +255 - added
Output schema / properties / cellCountAdded value: +{ + "description": "For 'pack': grid cells examined.", + "type": "integer" +} - added
Output schema / properties / columnsAdded value: +{ + "type": "integer" +} - added
Output schema / properties / formatAdded value: +{ + "type": "string" +} - added
Output schema / properties / layoutAdded value: +{ + "type": "string" +} - added
Output schema / properties / reusedExactAdded value: +{ + "description": "For 'pack': cells that matched an existing tile exactly.", + "type": "integer" +} - added
Output schema / properties / reusedFuzzyAdded value: +{ + "description": "For 'pack': cells merged by `tolerance`. A high number here with a low tolerance means the mockup has near-duplicate tiles worth cleaning up.", + "type": "integer" +} - added
Output schema / properties / rowsAdded value: +{ + "type": "integer" +} - added
Output schema / properties / skippedAdded value: +{ + "description": "For 'stamp': placements outside the grid or naming a tile that does not exist.", + "type": "integer" +} - added
Output schema / properties / sourceLayerAdded value: +{ + "description": "For 'pack': the mockup layer, now hidden.", + "type": "string" +} - added
Output schema / properties / tileHeightAdded value: +{ + "type": "integer" +} - added
Output schema / properties / tileWidthAdded value: +{ + "type": "integer" +}
- Changed
transform4 fields changed- removed
Input schema / properties / scopeRemoved value: -{ - "default": "selection", - "description": "What the transform applies to. 'selection' falls back to the cel when nothing is selected.", - "enum": [ - "selection", - "cel", - "layer", - "sprite" - ], - "type": "string" -} - changed
Input schema / properties / sprite / descriptionPrevious value: -"Sprite filename or id. Omit to use the sprite Aseprite has focused."New value: +"Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused." - removed
Output schema / properties / scopeRemoved value: -{ - "type": "string" -} - changed
Output schema / requiredPrevious value: -[ - "sprite", - "op", - "scope", - "pixelsChanged" -]New value: +[ + "sprite", + "op", + "pixelsChanged" +]
- Changed
validate1 field changed- changed
Input schema / properties / sprite / descriptionPrevious value: -"Sprite filename or id. Omit to use the sprite Aseprite has focused."New value: +"Which sprite: its id as '#7' (what every result reports back, and the only unambiguous form — two unsaved documents are both called 'Sprite'), its filename, or its display name. Omit to use the sprite Aseprite has focused."
18 tool updates
v0.1.0- First observed
cel - First observed
draw - First observed
export - First observed
frame - First observed
layer - First observed
look - First observed
palette - First observed
preflight - First observed
read_pixels - First observed
recolor - First observed
reference - First observed
select - First observed
sprite_info - First observed
sprite_manage - First observed
tag - First observed
tileset - First observed
transform - First observed
validate
TDQS
Scored across 18 tools
Most tools map cleanly to a distinct resource or action (draw, transform, recolor, layer, frame, cel, tag). A few boundaries blur slightly — look vs read_pixels (visual read vs structured pixel read) and draw vs transform vs recolor could be confused by an agent without reading the descriptions — but the descriptions themselves draw sharp lines (e.g. transform explicitly notes there is no selection-scoped transform).
There's a loose pattern (bare verbs for direct actions like draw/look/select/export, nouns for op-bundled resource managers like palette/layer/frame/cel/tileset), but it's not consistent — 'sprite_info', 'sprite_manage' and 'read_pixels' use snake_case while everything else is single-word, and 'preflight'/'validate' are neither verb_noun nor noun. Readable, but conventions are mixed.
18 tools for a full Aseprite editing surface (drawing, palette, layers, frames, tags, cels, selection, transform, export, tilesets, validation) is heavy but each tool earns its place via the op-bundling pattern that keeps related operations under one name. Slightly above the ideal 3-15 range.
Covers the full lifecycle: connection check (preflight), read state (sprite_info, look, read_pixels), palette, drawing, selection, transform, layer/cel/frame/tag management, recolor, validation, reference importing and export/tilesets. There is no obvious dead end for pixel-art creation and game-ready output.
Maintenance
Related MCP Connectors
Generate, edit, style-match, turn, and animate game-ready pixel art at exact sizes.
Generate pixel art sprites, animations, 8-direction rotations and palettes for games.
AI game assets for agents: consistent sprites, 2D animations, tiles, maps, music and engine exports.
Agent-Native design tool - create and edit visual designs with agent assistance
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables AI to create pixel art in Aseprite through pixel-level drawing primitives, read canvas screenshots, and iterate until satisfied.314MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to create and edit pixel art and animated sprites in Aseprite through 104 tools covering drawing, layers, animation, palettes, tilemaps, exports, visual analysis, and raw Lua scripting.116MIT
- AlicenseAqualityAmaintenanceEnables AI assistants to draw live in Aseprite, creating and editing sprites, using drawing tools, managing layers and frames, and viewing results as images.2237MIT
- AlicenseBqualityBmaintenanceEnables an AI agent to create and edit pixel art directly in Aseprite — building sprites, layers, frames, animation tags and palettes, painting pixels and primitives, inspecting the rendered result, and exporting GIFs or sprite sheets. All work lands on real .aseprite files that can be opened and edited by hand.431MIT