aseprite-ai-artist

Overview Schema Source Related Servers Discussions Admin

Preflight

preflight

Read-only

Check that Aseprite is connected and report what the session can do before editing pixel art, and stop if Aseprite is not ready. Choose live or headless mode only when the task requires it.

Instructions

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.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No	Switch the session to this Aseprite before checking. Omit to keep the current one.

Output Schema

TableJSON 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

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.4.0Sep 30, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / mode

Added value: +{
+  "description": "Switch the session to this Aseprite before checking. Omit to keep the current one.",
+  "enum": [
+    "live",
+    "headless"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / mode

Added 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"
+}

addedOutput schema / properties / switched

Added value: +{
+  "description": "True when this call changed the session's mode.",
+  "type": "boolean"
+}

changedOutput schema / required

Previous value: -[
-  "ready",
-  "bridgeConnected",
-  "pluginConnected",
-  "features",
-  "directive"
-]New value: +[
+  "ready",
+  "switched",
+  "mode",
+  "bridgeConnected",
+  "pluginConnected",
+  "features",
+  "directive"
+]

First observedv0.1.0Sep 8, 2026

TDQS

A4.3/5.0

Behavior2/5

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.

Conciseness5/5

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.

Completeness5/5

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.

Parameters4/5

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.

Purpose5/5

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.

Usage Guidelines5/5

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.

Deploy Server