Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

extract_palette_from_image

Extracts a median-cut color palette from an external image and sets it as the active Aseprite sprite palette by default. Returns hex colors sorted dark to light for locking concept-art palettes.

Instructions

Extract a palette (median-cut) from an external image file and, by default, set it as the active sprite's palette — the concept-art → locked-palette step. Returns the colors as hex, sorted dark→light. Headless: pass file.

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": {
      "image_path": "<image_path>"
    },
    "name": "extract_palette_from_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
replaceNo
image_pathYes
max_colorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/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 disclosure burden; it does disclose the important default mutation (overwrites the active sprite's palette) and the return shape (hex, dark→light). It does not say what happens to an existing palette when replace is true, whether the operation is reversible, or what occurs when no sprite is active.

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?

Three tight clauses, front-loaded with the core action and side effect, with no filler. The em-dash workflow gloss is compact and useful, though the 'Headless: pass file' fragment is slightly cryptic out of context.

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?

Covers the essential contract (extract from file, apply by default, return hex list) for a mutating tool with no output schema. With four undocumented parameters and no note on palette overwrite semantics or failure modes, it falls short of fully arming an agent to call it correctly in all cases.

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 coverage is 0% across four parameters. The description clarifies only 'file' for headless mode and gestures at the default behavior behind 'replace'; max_colors is never mentioned despite governing the median-cut output, and the interplay between the required image_path and the optional file parameter is left ambiguous.

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 (extract), resource (palette via median-cut), source (external image file), and the default side effect (sets it as the active sprite's palette), plus the workflow role ('concept-art → locked-palette step'). This is enough to distinguish it from palette_from_sprite, which reads a palette off a sprite rather than an external file.

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?

Implies usage through the workflow phrase and the 'Headless: pass file' note, which tells an agent how to run it without a UI context. But it never explicitly says when to choose this over palette_from_sprite or apply_bundled_palette, and gives no prerequisites or exclusions.

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