Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

set_palette

Replace an Aseprite file's entire color palette with a supplied list of #rrggbb or #rrggbbaa values, enabling consistent palette swaps for pixel art and game assets.

Instructions

Replace the whole palette with colors (list of #rrggbb/#rrggbbaa).

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": {
      "colors": "<colors>"
    },
    "name": "set_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
colorsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations carry only a title, so the description bears the full behavioral burden. It does disclose the key trait that this is an overwrite of the entire palette (existing colors are lost), which is the most important warning an agent needs. However, it says nothing about permissions, whether the change is undoable, or what happens to the undocumented `file` parameter.

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?

A single front-loaded sentence with no filler; the format hint sits in parentheses where it belongs. It is efficient, though verging on under-specified given the undocumented `file` parameter.

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?

With no output schema, no meaningful annotations, and 0% schema coverage on a two-parameter mutation tool, the description should do more. The destructive whole-palette overwrite is conveyed, but the `file` parameter's meaning and any post-call state or return information are absent.

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?

Schema description coverage is 0% across two parameters, so the description must compensate and only partly does. It usefully specifies the accepted color string formats (#rrggbb/#rrggbbaa), which the schema does not, but leaves the `file` parameter completely unexplained — an agent cannot tell whether it targets an on-disk palette file or an in-project one.

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?

"Replace the whole palette with colors" gives a specific verb (replace) and resource (whole palette), and the word "whole" implicitly contrasts with siblings like set_palette_color or add_palette_color that operate on single entries. It stops short of naming those alternatives explicitly, so the differentiation is inferable rather than stated.

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 only implied by the verb "replace the whole palette" — an agent can reason that this is for wholesale swaps rather than single-color edits. There is no explicit when-to-use statement, no mention of when to prefer set_palette_color/add_palette_color, and no prerequisites such as whether an active sprite or document must exist.

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