Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

draw_rectangle

Draw filled or outlined rectangles on the active Aseprite layer and frame with a hex color, optionally targeting a file and returning a before/after preview.

Instructions

Draw a rectangle on the active layer + frame. color is #rrggbb or #rrggbbaa. fill false draws only the outline. One undo step (live). Headless: pass file.

preview true also returns a before/after picture of the canvas with the changed-pixel count and bbox.

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": {
      "x": "<x>",
      "y": "<y>",
      "width": "<width>",
      "height": "<height>",
      "color": "<color>"
    },
    "name": "draw_rectangle"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
fileNo
fillNo
colorYes
widthYes
heightYes
previewNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior4/5

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

With no behavioral annotations beyond a title, the description carries the load and discloses that drawing affects the active layer/frame, creates one undo step, supports headless operation via file, and can return a before/after preview with changed-pixel count and bbox. It stops short of covering edge cases such as clipping, bounds behavior, or alpha compositing.

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 front-loaded with the core action and then compactly covers color, fill, undo behavior, headless mode, and preview. Every sentence adds useful 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 an 8-parameter drawing tool with no schema descriptions and no behavioral annotations, the description covers several important optional behaviors and undo semantics. However, it leaves the required geometry parameters and their coordinate semantics underspecified, and the output schema already covers return values so the description need not explain them.

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 0%, so the description must compensate. It meaningfully documents color format, fill behavior, file for headless use, and preview output, but leaves the core geometry parameters x, y, width, and height unexplained in terms of origin, units, or valid ranges.

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?

The description gives a specific verb and resource: 'Draw a rectangle'. It also states the target scope, 'active layer + frame', which makes the action concrete and distinguishes it from sibling shape-drawing tools like draw_circle or draw_ellipse.

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 description implies usage as a drawing primitive but does not explicitly say when to use this tool versus alternatives such as draw_circle or select_rectangle. It gives useful option-level guidance for fill, preview, and headless file usage, but no exclusions or alternative-tool routing.

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