aseprite-ai-artist

by with-pebbly

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Sprite info

sprite_info

Read-only

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.

Tool call template

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

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

Input 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

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.8.2Oct 12, 2026

addedOutput schema / properties / modified

Added value: +{
+  "description": "Unsaved changes present in this document.",
+  "type": "boolean"
+}

changedOutput schema / required

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

Changed5 schema fields changedv0.4.0Sep 30, 2026

changedOutput schema / properties / slices / items / properties / bounds / additionalProperties
```
Previous value: -{
-  "type": "number"
-}New value: +false
```

addedOutput schema / properties / slices / items / properties / bounds / properties

Added value: +{
+  "height": {
+    "exclusiveMinimum": 0,
+    "type": "integer"
+  },
+  "width": {
+    "exclusiveMinimum": 0,
+    "type": "integer"
+  },
+  "x": {
+    "type": "integer"
+  },
+  "y": {
+    "type": "integer"
+  }
+}

addedOutput schema / properties / slices / items / properties / bounds / required
```
Added value: +[
+  "x",
+  "y",
+  "width",
+  "height"
+]
```

addedOutput schema / properties / slices / items / properties / center

Added value: +{
+  "$ref": "#/properties/slices/items/properties/bounds",
+  "description": "Nine-slice centre region, relative to the slice. Only when set."
+}

addedOutput schema / properties / slices / items / properties / pivot

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "x": {
+      "type": "integer"
+    },
+    "y": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "x",
+    "y"
+  ],
+  "type": "object"
+}

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.1/5.0

Behavior4/5

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.

Conciseness4/5

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.

Completeness4/5

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.

Parameters3/5

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.

Purpose5/5

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.

Usage Guidelines4/5

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.

Deploy Server