Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

replace_color

Replaces all pixels matching a source color within a 0-255 RGB tolerance with a target color on the active cel, preserving alpha in one undo step; supports headless files.

Instructions

Replace every pixel matching from_color (within tolerance, a 0-255 RGB distance) with to_color across the active cel, preserving each pixel's alpha unless to_color carries its own. One undo step. Headless: pass file.

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": {
      "from_color": "<from_color>",
      "to_color": "<to_color>"
    },
    "name": "replace_color"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
to_colorYes
toleranceNo
from_colorYes

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 essentially nothing beyond a title, so the description bears the full disclosure burden and does well: it defines tolerance as a 0-255 RGB distance, states that alpha is preserved unless ``to_color`` carries its own, and declares that the operation is a single undo step. Gaps remain around what happens when no pixels match and what the tool returns, which keeps it from a 5.

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 carrying distinct information, with the core behavior front-loaded before the tolerance, alpha, undo, and headless details. No redundant restatement of the tool name or title.

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?

For a destructive color-mutation tool with no meaningful annotations and no output schema, the description covers the important surprises: reversibility (one undo step), alpha handling, tolerance units, and headless invocation. It falls short only on return/result reporting and no-match behavior, which an agent would otherwise have to discover by experiment.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, and it does for most parameters: ``from_color``/``to_color`` are explained by their role in the match-and-replace, ``tolerance`` is given a concrete unit and range (0-255 RGB distance), and ``file`` is tied to headless mode. It does not clarify what ``file`` should point at (path? project?) or what happens when it is omitted, leaving one parameter partly underspecified.

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?

The description states a specific verb and resource with scope: replace every pixel matching ``from_color`` with ``to_color`` across the active cel. It is unambiguous about what changes and where. It does not, however, contrast itself with the sibling ``select_by_color``, which is the nearest-looking alternative, so it stops short of a 5.

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?

Some usage context is given via 'Headless: pass ``file``', which tells the agent how to invoke the tool outside a GUI session. There is no explicit guidance on when to prefer this over ``select_by_color`` followed by a fill, and no exclusions or preconditions are named. Usage is implied rather than routed.

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