aseprite-ai-artist

Overview Schema Source Related Servers Discussions Admin

Manage sprites

sprite_manage

Destructive

Manage sprites in Aseprite by opening, creating, focusing, resizing, saving, and closing them. Also list open documents and adjust sprite properties.

Instructions

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'. Canvas resize keeps existing pixels — pass an anchor to say where they land.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`op`	Yes
`path`	No	File path for 'open' and 'save_as'.
`force`	No	Allow 'close' to discard unsaved changes. Ask the user before setting this.
`width`	No
`anchor`	No	Where existing pixels sit after 'resize_canvas'.	center
`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

TableJSON Schema

Name	Required	Description
`id`	No	Stable id of the affected document; pass it back as '#<id>'.
`op`	Yes
`path`	No
`width`	No
`height`	No
`sprite`	No
`sprites`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.1.6Sep 9, 2026

changedInput schema / properties / sprite / description

Previous 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."

addedOutput schema / properties / id

Added value: +{
+  "description": "Stable id of the affected document; pass it back as '#<id>'.",
+  "type": "integer"
+}

addedOutput schema / properties / sprites / items / properties / colorMode
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / sprites / items / properties / frames
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / sprites / items / properties / id
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / sprites / items / properties / layers
```
Added value: +{
+  "type": "integer"
+}
```

changedOutput schema / properties / sprites / items / required

Previous value: -[
-  "name",
-  "width",
-  "height",
-  "active",
-  "modified"
-]New value: +[
+  "id",
+  "name",
+  "width",
+  "height",
+  "colorMode",
+  "frames",
+  "layers",
+  "active",
+  "modified"
+]

First observedv0.1.0Sep 8, 2026

TDQS

B3.1/5.0

Behavior3/5

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 known. The description adds one behavioral detail: 'Canvas resize keeps existing pixels — pass an anchor to say where they land.' This is useful, but it does not disclose other side effects like overwriting files on save or the impact of 'activate' on the session focus, relying on the schema for such details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, efficient and front-loaded with the primary purpose. The list of ops is clear, and the anchor note is appended logically. No wasted words, though a slightly structured breakdown per op could improve it without adding much length.

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

Completeness2/5

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

This is a complex tool with 9 ops and 9 parameters. The description only gives an overview and one behavioral detail, leaving many op-specific semantics (e.g., what 'set_properties' does, prerequisites for 'save_as', return formats) implicit. The output schema exists, so returns are covered, but the description does not adequately guide an agent on when and how to use each op, especially for a destructive tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 67%, so many parameters already have descriptions. The description adds meaning for the 'anchor' parameter by explaining that resize keeps existing pixels and anchor controls their placement. Other parameters like op, width, height are left to the schema, and the description does not compensate for the 33% gap.

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

Purpose4/5

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

The description states a clear purpose: 'Open, create, focus, resize, save and close sprites in the running Aseprite session.' It lists the ops explicitly and gives a specific resource (sprites) and session context. However, it does not explicitly differentiate from sibling tools like sprite_info, so it lacks a direct contrast, but the verb+resource is specific enough.

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

Usage Guidelines2/5

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

The description does not provide explicit when-to-use or when-not-to-use guidance relative to sibling tools. It lists operations but never states alternatives or exclusions, such as 'use sprite_info for reading sprite data.' The context is implied but not directly addressed.

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

Deploy Server