Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

set_palette_color

Idempotent

Set a palette entry at a specific index to a hex color (#rrggbb or #rrggbbaa), letting you correct or update individual palette slots in an Aseprite file.

Instructions

Set palette entry index to color (#rrggbb or #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": {
      "index": "<index>",
      "color": "<color>"
    },
    "name": "set_palette_color"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
colorYes
indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotations provide only idempotentHint=true and a title; the description adds only the color literal syntax and says nothing about mutation effects on existing entries, index validity, or what the optional file parameter targets. With no explanation of how the optional file argument changes the target palette, an agent cannot predict the effect of omitting it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with the effect front-loaded and no filler. Every clause carries information the caller needs, though the brevity is also where its gaps originate.

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?

For a three-parameter mutation tool with no output schema and minimal annotations, the definition should cover the optional file argument and index validity. Leaving one of three parameters undocumented makes it incomplete relative to the tool's surface.

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 explains index and color (including #rrggbb vs #rrggbbaa), which is the key semantic detail, but leaves the file parameter entirely unexplained, so it only partially fills the gap.

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 and resource: sets a palette entry at a given index to a given color. It also specifies the accepted color literal format. It does not explicitly differentiate itself from siblings like set_palette or add_palette_color, but the operation is clear on its own.

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?

There is no guidance on when to use this versus set_palette, add_palette_color, or replace_color, which all appear adjacent. It also does not state whether the index must already exist or whether this overwrites an existing entry. The agent must infer all routing from the name.

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