Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

draw_on_tile

Set pixels on one tile in a tilemap layer's tileset, updating every placed instance at once. Pass the layer, tile index, and {x, y, color} pixels; overflow pixels are skipped and edits commit as one undo step.

Instructions

Set pixels on one tile of a tilemap layer's tileset. pixels is a list of {x, y, color} objects (color #rrggbb or #rrggbbaa; x/y relative to the tile's top-left). Pixels outside the tile are skipped and counted. Every placed instance of the tile updates. One undo step. Headless: pass file.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "layer": "<layer>",
      "tile_index": "<tile_index>",
      "pixels": "<pixels>"
    },
    "name": "draw_on_tile"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
layerYes
pixelsYes
tile_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior4/5

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

With no behavioral annotations, the description carries the burden and supplies important effects: out-of-tile pixels are skipped and counted, every placed instance of the tile updates, and the action is one undo step. It also notes the headless file parameter, though it does not describe the return payload 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?

The description is compact and front-loaded: purpose first, then the complex pixels format, then side effects and undo/headless notes. Every sentence adds useful information and there is no 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?

For a mutating drawing tool with no annotations and no output schema, the description covers pixel format, boundary behavior, instance propagation, undo, and headless mode. It still leaves the return value or count and layer/tile_index validity or error behavior implicit, so it is adequate but not fully complete.

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 description coverage is 0%, so the description must define the parameters; it explains pixels as {x, y, color} objects with hex color formats and tile-relative coordinates, and explains the file parameter for headless use. Layer and tile_index are only contextually defined as a tilemap layer and a tile in its tileset, which is adequate but not exhaustive on indexing or valid ranges.

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?

The description states a specific verb, 'Set pixels', and a specific resource, 'one tile of a tilemap layer's tileset', so the operation is clear. It does not explicitly contrast with sibling tools like draw_pixels, but the tile-specific scope is distinctive.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, prerequisites, or named alternative tools; the only contextual cue is 'Headless: pass file'. An agent must infer from the description that this is for drawing onto tilemap tiles rather than canvas pixels.

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

Deploy Server

Other Tools