Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

fill_area

Flood-fills a contiguous same-color region at the given x,y coordinates with a chosen color, creating one undo step and optionally returning a before/after preview.

Instructions

Flood-fill the contiguous same-color region at (x, y). Most reliable on RGB sprites. One undo step. 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>",
      "color": "<color>"
    },
    "name": "fill_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
fileNo
colorYes
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?

Annotations carry only a title, so the description carries the behavioral burden and does reasonably well: it discloses that the operation is an undoable mutation ('One undo step') and that preview returns a before/after picture plus changed-pixel count and bbox. It still doesn't say what happens on out-of-bounds coordinates or whether the fill respects selection/layer boundaries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short and front-loaded: the core operation comes first, then reliability, then undo and headless/preview notes. The only mild inefficiency is that the preview behavior and the headless note are separate fragments rather than grouped by parameter.

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?

An output schema exists, so return values need not be restated, and the description covers the mutation/undo semantics and preview mode. The remaining gap is parameter-level detail for coordinates and color on a five-parameter mutation tool with no annotations.

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 explains file (headless usage) and preview (before/after image with count and bbox), but leaves x/y coordinate origin/units and the accepted color format (hex, name, palette index) undefined.

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 opens with a specific verb and resource: 'Flood-fill the contiguous same-color region at (x, y).' That distinguishes it from erase_area and fill_polygon without needing the schema, and it names the exact target of the operation.

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?

It gives one useful applicability hint ('Most reliable on RGB sprites') and a mode-specific instruction ('Headless: pass file'), but it never states when to prefer this over erase_area or fill_polygon, nor any exclusions or prerequisites.

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