Skip to main content
Glama
Sign In
Aseprite MCP

Aseprite MCP

by MalloyTheDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_palette_color

Set or replace a specific palette entry by its 0-based index, automatically expanding the palette when the index exceeds the current size.

Instructions

Set a single palette entry by index (0-based). Grows the palette if needed.

The index is bounded by the palette ceiling: the Lua below resizes the palette to
`index + 1`, so the index *is* a palette size.

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>",
      "index": "<index>",
      "color": "<color>"
    },
    "name": "set_palette_color"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorYes
indexYes
filenameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.10.0
    • removedInput schema / properties / color / title
      Removed value: -"Color"
    • removedInput schema / properties / filename / title
      Removed value: -"Filename"
    • removedInput schema / properties / index / title
      Removed value: -"Index"
    • removedInput schema / title
      Removed value: -"set_palette_colorArguments"
  2. First observedv0.7.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false, so the description carries real weight by disclosing that the palette grows if the index exceeds its size — a mutation side-effect the agent would otherwise not anticipate. It does not explain return values, error behavior, or whether color must be a specific format, which keeps it from a 5.

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?

Front-loaded with the core action and two sentences of genuinely relevant constraint, with no filler. The dangling reference to 'the Lua below' is a minor structural flaw since no such code is present in the visible definition.

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?

With no output schema and thin annotations, the description covers the mutation and index semantics but leaves the color encoding and filename target unspecified. It is adequate to call the tool safely but not fully self-contained.

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 for three parameters. It usefully clarifies that index is 0-based and effectively defines the resulting palette size, but it says nothing about the color string format or the filename parameter's role, leaving meaningful gaps.

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+resource (set a single palette entry) and scope (by index, one entry at a time), which distinguishes it from bulk siblings like set_palette and resize_palette. It never names an alternative explicitly, so it falls short of a 5 but the operation is unmistakable.

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: an agent can infer this is for writing one entry rather than the whole palette or appending a new one, but the description never states when to prefer it over add_palette_color, set_palette, or resize_palette. The growth note hints at a use case but no explicit routing guidance is given.

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