aseprite-mcp

aseprite_view

Render a frame to PNG to visually inspect pixel art, and optionally return an ASCII map for precise pixel position and color verification before finishing.

Instructions

Render a frame to a PNG image so you can actually LOOK at the artwork and judge it. Use this after drawing, and before telling the user the piece is finished. Set includeAscii: true to also get an exact character map of the pixels, which is the most precise way to verify positions and colours.

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": "aseprite_view"
  }
}

Input Schema

Name	Required	Description
`frame`	No	Zero-based frame index (omit for the first frame).
`scale`	No	Integer zoom for the rendered image (default: automatic).
`layers`	No	Render only these layers.
`document`	No	Document to act on: a short name inside the art folder ("hero"), a relative path, or an absolute .aseprite path. Omit to use the active document.
`includeAscii`	No	Also return a character map of the frame.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 27, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the dual output mode (PNG plus optional ASCII character map) and hints at the verification purpose, but says nothing about whether the document is mutated, where the PNG goes, or how the render is returned to the agent.

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?

Front-loads the core action in the first clause and keeps the whole thing to a few tightly packed sentences. The parenthetical workflow advice ("before telling the user the piece is finished") is slightly chatty but earns its place as usage guidance.

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

Completeness3/5

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

No output schema and no annotations, so the description should disclose what actually comes back. It explains the ASCII alternative but not the PNG return shape or scale/layers defaults, leaving a gap for a tool whose entire value is the rendered result.

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 100%, so all five parameters are already documented. The description only re-states includeAscii ("also get an exact character map") and adds no syntax or interaction detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ("Render a frame to a PNG image") and frames the intent as inspecting artwork rather than exporting it, which implicitly separates it from aseprite_export_png and aseprite_export_sprite_sheet. It never names those siblings, so the differentiation is left to inference.

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?

Gives concrete timing guidance ("Use this after drawing, and before telling the user the piece is finished"), which tells the agent when in the workflow to call it. There is no explicit when-not or named alternative, keeping it 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.

Deploy Server