Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

match_palettes

Unify colors across open sprites or files by merging near-duplicate shades into the most-used color within a tolerance, preserving alpha and adding one undo step per sprite.

Instructions

Put sprites of one character or set on one shared palette: colours closer than tolerance that stand in for each other (one sprite uses one, another sprite the other) merge into whichever is used most, across the open sprites (live; only picks them by filename or tag) or files. Alpha is kept. One undo step per sprite. Check first with check_consistency.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "match_palettes"
  }
}

Input Schema

NameRequiredDescriptionDefault
onlyNo
filesNo
toleranceNo

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 only supply a title ('Merge sprites onto one palette') with no readOnly or destructive hints, so the description carries the burden and does add real behaviour: alpha is preserved, the merge resolves to the most-used colour, and there is 'one undo step per sprite'. It does not describe whether live edits are visible immediately, what happens on failure, or what the response contains.

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

Conciseness3/5

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

Everything in the text is relevant, and the action is front-loaded, but the single run-on sentence with nested parentheses and double-backtick markup is hard to parse at speed. It would benefit from being split into action, targeting, and side-effect sentences.

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 three-parameter mutation tool with no output schema and only a title annotation, the description covers purpose, both targeting modes, the merge rule, and undo granularity. The remaining gap is that no return-value or failure behaviour is given, though an output schema is absent so this is a minor omission.

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 largely does: 'tolerance' is framed as the colour-distance threshold for merging, 'only' selects live open sprites by filename or tag, and 'files' targets file paths, with a stated default of 0.045. It omits the units or valid range for tolerance, leaving the scale ambiguous.

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 names a specific verb and resource: putting sprites of one character or set onto one shared palette by merging near-duplicate colours. It also implicitly distinguishes itself from verification-only tooling by pointing to check_consistency. Parsing is somewhat difficult because the core action is buried in a long clause with parentheticals, which keeps it 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states a pre-check workflow ('Check first with check_consistency') and explains the two targeting modes: 'across the open sprites (live; only picks them by filename or tag)' versus 'files'. It does not say when to prefer this over sibling palette tools such as batch_apply_palette or apply_preset_palette, so exclusions are absent.

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