Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

apply_dither

Fills a rectangle with a Bayer 4x4 dither that blends two colors by density, returning an optional before/after preview with changed-pixel count and bounding box.

Instructions

Fill a rectangle with a uniform ordered (Bayer 4x4) dither mixing color1 and color2. density 0..1 is the fraction of color2 — 0.5 is an even checker-style mix. 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>",
      "width": "<width>",
      "height": "<height>",
      "color1": "<color1>",
      "color2": "<color2>"
    },
    "name": "apply_dither"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
fileNo
widthYes
color1Yes
color2Yes
heightYes
densityNo
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 supply only a title, so the description carries the load and does add real behavior: one undo step (reversibility), a headless mode selector via `file`, and the fact that `preview` returns a before/after image with changed-pixel count and bbox. It stops short of stating failure behavior for out-of-bounds rectangles or whether pixels are set unconditionally.

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 paragraphs, front-loaded with the verb and resource, then behavior and preview mode. No filler sentences and no restatement of the tool name.

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?

An output schema exists so return values need not be enumerated, and the undo/headless notes cover much of the behavioral surface for a 9-parameter mutation tool. However, with zero schema coverage on nine parameters, the missing color-format and coordinate/out-of-bounds details are material gaps an agent must guess at.

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 `color1`/`color2`, `density` (0..1, fraction of color2, 0.5 = even mix), `file` (headless), and `preview`. It leaves `x`/`y`/`width`/`height` semantics (coordinate space, bounds handling) and the accepted color format entirely unstated.

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?

Names a specific operation (fill a rectangle with an ordered Bayer 4x4 dither) plus the two colors it mixes, which makes it immediately distinguishable from siblings like apply_shading or the palette tools. No opening ambiguity about what the tool produces.

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 implied by the mechanics (dither mixes two colors by density) but the description never says when to prefer this over apply_shading, apply_bundled_palette, or a plain fill, and gives no exclusions or prerequisites. The density explanation helps the agent pick argument values rather than pick the tool.

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