Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

fill_polygon

Fill any polygon in Aseprite by scanning line-filling a list of ordered [x, y] points with a solid color in one undoable step, optionally returning a before/after preview.

Instructions

Scanline-fill an arbitrary polygon given points (a list of [x, y] pairs, in order). color is #rrggbb or #rrggbbaa. 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": {
      "points": "<points>",
      "color": "<color>"
    },
    "name": "fill_polygon"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
colorYes
pointsYes
previewNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/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 does the behavioral work: it discloses that the operation is a single undo step, that preview changes the return payload (before/after image plus changed-pixel count and bbox), and that headless use requires file. It stops short of stating coordinate space, clipping behavior, or what happens for self-intersecting polygons.

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?

Four short sentences, each front-loading a distinct fact (operation, color format, undo cost, headless mode, preview side effect) with no filler or repetition.

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 explained, and the description still notes the extra preview payload. Given a four-parameter drawing mutation with essentially no annotations, it covers the essentials but leaves coordinate space, degenerate-input handling, and sibling differentiation unaddressed.

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?

Schema description coverage is 0%, so the description must carry all four parameters, and it does: points is defined as an ordered list of [x, y] pairs, color as #rrggbb or #rrggbbaa, preview as enabling the extra before/after return, and file as the headless target. That is full semantic coverage despite the empty schema.

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 ("scanline-fill an arbitrary polygon") plus the operation's shape, which is far more informative than the bare name. It does not name or contrast with the sibling fill_area, so the agent must infer the distinction between polygon fill and area fill itself.

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 context is implied by the mechanics: "Headless: pass file" tells the agent when the file parameter applies, and "one undo step" signals it is an undoable edit. There is no explicit statement of when to choose this over fill_area or other paint operations, and no prerequisites are given.

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