aseprite-ai-artist

Overview Schema Source Related Servers Discussions Admin

Sprite info

sprite_info

Read-only

Retrieve the complete structural state of a sprite, including dimensions, palette, layers, frames, tags, slices, and current selection, to inform accurate edits.

Instructions

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.

Input Schema

TableJSON Schema

Name	Required	Description
`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

TableJSON 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
`colorMode`	Yes
`selection`	No
`frameCount`	Yes
`activeFrame`	No
`activeLayer`	No
`transparentIndex`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 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 for this open document. Pass it back as '#<id>'.",
+  "type": "integer"
+}

removedOutput schema / properties / tags / items / properties / repeat

Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

addedOutput schema / properties / tags / items / properties / repeats

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Loop count; 0 means forever."
+}

changedOutput schema / required

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

First observedv0.1.0Sep 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The readOnlyHint annotation already signals safety, and the description adds meaningful context: it guarantees a 'full structured state' and explains the failure mode of proceeding without it. No contradiction with annotations exists.

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

Conciseness5/5

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

Two dense sentences with zero filler. The state inventory is front-loaded, and the critical usage warning follows immediately. Every sentence earns its place.

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

Completeness5/5

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

An output schema exists, so return shape is covered. The description enumerates the state contents, provides a clear usage rule, and annotations cover read-only safety. With no required parameters and no unusual behavior, nothing essential is missing for correct invocation.

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?

The schema already documents sprite and includePalette; includeSlices is merely named in the schema. The description mentions palette and slices as part of the state, which reinforces the toggles, but it doesn't explain defaults or how includeSlices changes the result. With 67% schema coverage, the description adds only modest value over the schema.

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

Purpose5/5

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

The description states a specific purpose: return the full structured state of a sprite, with a detailed inventory of exactly what is included (dimensions, layers, frames, tags, slices, selection). It also frames the tool as a read-before-editing operation, clearly distinguishing it from mutation/drawing siblings.

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

Usage Guidelines4/5

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

The description explicitly says to read this before editing and warns that guessing at layer names or frame counts corrupts files, giving a clear trigger for when to use this tool. It doesn't name alternative tools for other read purposes, but the when-to-use guidance is strong.

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

Deploy Server