Skip to main content
Glama
ZeroTian

Aseprite MCP Tools

by ZeroTian

draw_on_tile

Draw pixels onto a tile in a tilemap layer's tileset, using tile-local coordinates. Appends a new tile when tile_index exceeds current count.

Instructions

Draw pixels onto a tile in a tilemap layer's tileset.

Coordinates are tile-local (0,0 = tile top-left). When tile_index equals the current tile count, a new tile is appended automatically.

Args: filename: Aseprite file to modify layer_name: Tilemap layer whose tileset to edit tile_index: Tile to draw on (1 = first real tile; 0 is reserved for the empty tile and cannot be drawn on) pixels: List of {"x": int, "y": int, "color": "#RRGGBB"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameYes
layer_nameYes
tile_indexYes
pixelsYes
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses key behaviors: tile_index 0 is invalid, auto-append when tile_index equals current count, and that the tool modifies an Aseprite file. However, it does not mention undo capabilities, permission requirements, or error conditions.

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?

Description is concise: a one-sentence purpose followed by a structured list of arguments. Every sentence is informative and there is no redundancy or filler.

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?

Description covers key aspects but lacks return value information and error handling details (e.g., behavior when tile_index is invalid except for note about 0 and auto-append). Given no output schema, a hint about what the tool returns would improve completeness.

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

Parameters5/5

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

Schema has 0% description coverage, so description explains all 4 parameters clearly: filename, layer_name, tile_index (1-based index, 0 reserved), and pixels (format). This adds essential meaning beyond the schema's type-only information.

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?

Description clearly states it draws pixels onto a tile in a tilemap layer's tileset, with tile-local coordinates. This distinguishes it from sibling tools like draw_pixels (general pixel drawing) and set_tiles (sets entire tiles). The verb and resource are specific and unambiguous.

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

Usage Guidelines3/5

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

Description provides contextual help (tile-local coordinates, auto-append) but does not explicitly compare to alternative tools for tilemap editing such as set_tiles or get_tile_at, nor does it state when not to use this tool. Some usage guidance is present but not comprehensive.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ZeroTian/aseprite-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server