Skip to main content
Glama
Sign In
aseprite-mcp

aseprite-mcp

by shin2344234
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

draw_image

Composite or overwrite PNG images into an Aseprite layer or frame at specific coordinates, with optional crop, scaling, and blend/copy/replace modes.

Instructions

Draws an image file (PNG, etc.) into a layer/frame at (x,y). mode 'blend' composites over existing pixels, 'copy' overwrites the area, 'replace' swaps the whole cel image. Optional source crop, scale or target size.

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": {
      "file": "<file>"
    },
    "name": "draw_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
fileYes
modeNo
saveNoBatch mode: write changes back to the sprite file (default true)
frameNo1-based frame number. Defaults to the active frame (or 1).
layerNoLayer name, 'Group/Child' path, or 1-based index from get_sprite_info. Defaults to the active layer.
scaleNo
widthNo
heightNo
spriteNoFile path, open tab title, or sprite id. Defaults to the active sprite (live). Batch mode needs a file path.
backendNoauto (default): live Aseprite if connected, else headless batch
opacityNo
blendModeNo
sourceRectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

The description goes beyond the annotations by defining each mode's effect: 'blend' composites, 'copy' overwrites the area, 'replace' swaps the whole cel image. That is real behavioral disclosure for a mutating tool whose annotations only say readOnly=false/destructive=false. It does not mention undo/reversibility or that batch mode writes to disk, which would complete the picture.

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?

Two tight sentences, front-loaded with the core action and destination, then mode semantics, then the optional transforms. Every clause adds information with 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 15-parameter mutation tool with no output schema and minimal annotations, the description covers the destination and modes but omits return/error behavior, undo implications, and the live-vs-batch save semantics. It is enough to attempt a basic call but not enough to use the tool confidently across backends.

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 description coverage is low (33%), so the description must carry weight, and it does explain mode semantics plus the existence of source crop, scale and target size. However, it says nothing about x/y placement origin, opacity, blendMode, frame/layer/sprite resolution, or the save/batch distinction, leaving many of the 15 parameters undocumented in both places.

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 ('Draws an image file (PNG, etc.) into a layer/frame at (x,y)'), which implicitly separates it from draw_pixels, draw_shapes and draw_text by input type. No sibling is named explicitly, so an agent must infer the boundary rather than being told it.

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?

Usage is only implied: you use it when you have an image file to place. There is no explicit 'use this instead of draw_pixels/draw_shapes when...' guidance, and no note about when live vs batch backend is required (only the schema covers backend/save).

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