Skip to main content
Glama
Sign In
Aseprite MCP

Aseprite MCP

by MalloyTheDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_palette

Destructive

Replace a sprite's entire color palette with a given list of colors to apply programmatic color updates for Aseprite pixel art and animation projects.

Instructions

Replace the entire palette with the given list of colours.

colors: list of colour strings, e.g. ["#000000", "#ffffff", "255,0,0"].

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

Input Schema

NameRequiredDescriptionDefault
colorsYes
filenameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.10.0
    • removedInput schema / properties / colors / title
      Removed value: -"Colors"
    • removedInput schema / properties / filename / title
      Removed value: -"Filename"
    • removedInput schema / title
      Removed value: -"set_paletteArguments"
  2. First observedv0.7.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, and the description's 'Replace the entire palette' largely restates that rather than adding context. It says nothing about what 'filename' scopes to (which sprite/palette file), whether the previous palette is recoverable, or what happens to palette indices already in use.

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?

Two short lines, front-loaded with the destructive action and then the one non-obvious parameter format. The trailing fragment 'colors: ...' is slightly terse but not wasteful.

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

Completeness3/5

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

For a destructive, file-scoped mutation with no output schema, the description is minimally adequate: it conveys the overwrite semantics and the colour format. It omits what 'filename' refers to and any recoverability/permission note, which matters given destructiveHint=true.

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

Parameters3/5

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

Schema coverage is 0%, so the description must compensate. It does document the 'colors' parameter with concrete format examples (hex and 'r,g,b' strings), which is genuinely useful, but the required 'filename' parameter is never explained, leaving half the inputs 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?

States a specific verb ('Replace') plus resource ('palette') and scope ('entire'), which distinguishes it from partial mutators like add_palette_color or set_palette_color. It does not explicitly name those siblings, but the scoping word 'entire' carries the differentiation.

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 when-to-use guidance and no mention of alternatives, despite a dense sibling cluster (set_palette_color, add_palette_color, resize_palette, load_palette, quantize_palette). The agent is left to infer that this is the whole-palette overwrite variant.

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