Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

palette_from_sprite

Derive a new hex color palette from a sprite's actual pixels using Aseprite color quantization, with a configurable maximum color count and one undo step.

Instructions

Derive the palette FROM the sprite's actual pixels (Aseprite's color quantization) — the inverse of quantize_to_palette. Returns the new palette as hex. One undo step.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "palette_from_sprite"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
max_colorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

With no behavioral annotations, the description carries the burden and does well: it discloses the underlying engine ('Aseprite's color quantization'), the return format (new palette as hex), and mutation semantics ('One undo step'). It does not say whether the sprite's existing palette is replaced or whether the new palette is persisted, which is the main remaining gap.

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?

Two tight sentences with the key contrast and return value front-loaded; no filler or redundant restatement of the title.

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 two-parameter, no-output-schema tool it covers the outcome and undo behavior adequately, but omits parameter meaning and whether the result is applied to the sprite or only returned, leaving an agent to guess at call correctness for max_colors and file.

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%, so the description must explain the two parameters and it mentions neither. The file parameter (nullable, defaults to null — presumably active sprite) is completely unexplained, and max_colors is only obliquely implied by 'color quantization' without stating that it caps the derived palette size.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Derive the palette from the sprite's actual pixels') and explicitly distinguishes itself from the inverse sibling quantize_to_palette. An agent can tell exactly what this produces without inspecting the schema.

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

Usage Guidelines4/5

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

The phrase 'the inverse of quantize_to_palette' gives clear directional guidance: use this to extract a palette from existing pixels rather than remap pixels to a given palette. It stops short of stating explicit exclusions or preconditions, so it is clear context without full when/when-not.

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