Aseprite-MCP

Overview Schema Source Related Servers Discussions Admin

recolor_palette

Recolor a sprite's palette by providing a mapping of original colors to replacement colors. Apply color substitutions to an image file.

Instructions

Recolors the palette based on a mapping of from->to colors

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": {
      "saveOutput": "<saveOutput>",
      "mapping": "<mapping>",
      "inputFile": "<inputFile>"
    },
    "name": "recolor_palette"
  }
}

Input Schema

Name	Required	Description	Default
`mapping`	Yes
`inputFile`	Yes
`saveOutput`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Jul 5, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations provided; the description fails to disclose side effects (e.g., whether the input file is overwritten), authentication requirements, or behavioral details beyond a basic operation.

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?

The description is very short and efficient, but at the cost of omitting essential information. It is not bloated, but it is under-specified.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given three required parameters, no output schema, and no annotations, the description lacks critical details such as parameter formats and expected behavior.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description only hints at the 'mapping' parameter but does not explain the format of mapping, nor the roles of 'inputFile' and 'saveOutput'.

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 clearly states the tool recolorals the palette using a color mapping. However, it does not differentiate from sibling tools, some of which may also modify the palette.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, nor any prerequisites or context for usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.