Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

recolor_variants

Batch-recolor sprite colors into named team or seasonal variants, export one comparison strip per variant to a directory, and report unmatched colors while leaving the source untouched.

Instructions

Recolor the sprite into team colors or seasons in one batch. variants maps each variant's name to a color swap, like {"red": {"#3050c0": "#c03030"}, "green": {"#3050c0": "#30a040"}}. Writes one strip <name>_<variant>.png per variant into output_dir, frames left to right, and returns a picture comparing them. Colors must match exactly, and any that were never found are listed in unmatched. Leaves the sprite untouched. tag limits it to one animation. 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": {
      "variants": "<variants>",
      "output_dir": "<output_dir>"
    },
    "name": "recolor_variants"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
fileNo
nameNo
variantsYes
output_dirYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations it discloses concrete behavior: file artifacts ('writes one strip <name>_<variant>.png per variant into output_dir'), the comparison image returned, the exact-match color requirement, the 'unmatched' list for missed colors, and that the source sprite is untouched (consistent with destructiveHint=false). Only gaps are overwrite/conflict handling for existing files in output_dir.

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?

Information is front-loaded: purpose, then the variants structure with an example, then outputs, then the matching caveat, then optional params. Sentences are dense but each carries behavior; the telegraphic final fragment ('Headless: pass file.') is efficient rather than wasteful.

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 tool with a nested-object parameter, 5 params, no schema descriptions and no output schema, the description covers inputs, on-disk artifacts, return value and color-matching failure mode. Only the 'name' parameter and output_dir collision behavior are unaddressed.

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 coverage is 0% across 5 parameters, so the description must compensate, and it largely does: 'variants' is explained as name→color-swap mapping with a worked example, 'output_dir' as the write target, 'tag' as an animation filter, and 'file' as the headless entry point, plus the nested structure (variant name to hex pair map) the schema type alone does not make obvious. The 'name' parameter is left undocumented, which is the one real hole.

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 opens with a specific verb and resource ('Recolor the sprite') and adds the scope ('into team colors or seasons in one batch'), so the operation is unambiguous. It never names a sibling or explains why this differs from palette-oriented tools, which keeps it at a 4 rather than 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?

Use context is implied by 'team colors or seasons in one batch' and clarified by 'tag limits it to one animation' and 'Headless: pass file'. There is no explicit when-not guidance or named alternative (e.g. the palette/batch tools in the catalog), so an agent must infer routing.

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