Skip to main content
Glama

aseprite_draw

Draw geometric primitives, lines, shapes, text, fills, gradients, and dithering onto sprite layers and frames in one ordered batch call.

Instructions

Draw geometric primitives. Pass ops: an array of drawing operations applied in order, all in one call. Coordinates are 0-based from the top-left.

Operations: {op:"pixel", x, y, color} one pixel {op:"line", x1, y1, x2, y2, color} Bresenham line {op:"rect", x, y, w, h, color, filled:false} rectangle (w/h in pixels) {op:"ellipse", cx, cy, rx, ry, color, filled:false} ellipse; rx=ry for a circle {op:"polygon", points:[[x,y],...], color, filled:false} {op:"spline", points:[[x,y],...], color} smooth Catmull-Rom curve (good for tails, hair, limbs) {op:"fill", x, y, color, tolerance:0} flood fill from a seed pixel {op:"clear", x, y, w, h} make a region transparent {op:"gradient", x, y, w, h, from, to, bands:8, direction:"vertical"} banded ramp (classic pixel-art shading) {op:"dither", x, y, w, h, colors:[a,b], matrix:"bayer4", ratio:0.5} ordered dithering {op:"pattern", x, y, w, h, tile:[["#111","."],["#222","#333"]]} repeating 2-D tile {op:"text", text:"Hi", x, y, color, scale:1} built-in 5x7 pixel font

Each op may override layer and frame. Colors accept "#rrggbb", "#rrggbbaa" or a name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opsYesDrawing operations, applied in order.
frameNoDefault target frame for every op.
layerNoDefault target layer for every op.
documentNoDocument 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses useful traits: ops apply in order, coordinates are 0-based from top-left, each op may override layer/frame, and 'clear' makes regions transparent. However, it is silent on side effects like whether drawing requires an open document, undo/reversibility, whether a missing layer auto-creates, and error behavior.

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 purpose and the key 'ops applied in order' mechanic, then a dense but well-aligned op reference table. Every line documents a distinct operation or coordinate/color convention; nothing is redundant filler.

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

Completeness4/5

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

Given no output schema and no annotations, the description is strong on input semantics and op behavior. Minor gaps remain around document creation requirements, failure behavior, and interaction with the active document when 'document' is omitted, but an agent has enough to invoke correctly.

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?

Top-level schema coverage is 100% for document/frame/layer/ops, but the ops array is additionalProperties:true with only 'op' documented, so the description carries essentially all op-level parameter semantics: per-op fields (x, y, w, h, cx, cy, rx, ry, points, tolerance, bands, matrix, ratio, tile, scale) plus the '#rrggbb'/'#rrggbbaa'/name color formats. This is substantial added meaning well beyond the schema.

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 ('Draw geometric primitives') and immediately enumerates the exact drawing operations supported, making it distinguishable from siblings like aseprite_fill_regions, aseprite_text, and aseprite_pixels. An agent can tell what this tool produces without opening the schema.

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?

The op catalog implies usage (use 'fill' for flood fill, 'text' for text, 'spline' for curves), but there is no explicit when-to-use guidance or routing against overlapping siblings such as aseprite_fill_regions, aseprite_text, or aseprite_draw_across_frames. Usage must be inferred from the operation list.

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