Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

quantize_to_palette

Snap opaque pixels to the nearest palette color while preserving alpha, enforcing palette discipline after intake or shading in RGB sprites.

Instructions

Snap every opaque pixel of the active cel to its nearest color in the sprite's palette (alpha preserved) — enforce palette discipline after intake or shading. RGB sprite; one undo step. Headless: pass file.

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": "quantize_to_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

With only a title annotation, the description carries the burden well: it discloses that only opaque pixels are touched, alpha is preserved, the sprite must be RGB, and the whole thing is one undo step (so it is reversible). It stops short of saying what happens on a non-RGB sprite (error vs. no-op) or whether a selection is respected.

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?

The core operation is front-loaded in the first clause, followed by purpose context, then two terse constraint statements ('RGB sprite; one undo step. Headless: pass file'). No sentence is wasted.

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

Completeness4/5

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

For a one-parameter tool with no output schema and no annotations, the definition covers operation, constraints, reversibility, and the headless path. Remaining gaps are minor: return behavior and failure modes on unsupported sprites are unstated.

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% for the single 'file' parameter, so the description must compensate, and it does partially by explaining that passing 'file' selects the headless mode. It does not say what the value should be (path, format, expected content), so the compensation is only partial.

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?

The description names a precise operation: snapping every opaque pixel of the active cel to its nearest palette color, with alpha preserved. That is a specific verb-plus-resource statement an agent can act on. It does not explicitly contrast with palette-applying siblings such as apply_preset_palette or apply_bundled_palette, so it falls short of a 5.

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?

The phrase 'enforce palette discipline after intake or shading' implies the intended workflow, and 'Headless: pass file' indicates the alternative invocation mode. However, there is no explicit statement of when NOT to use this versus the palette-application siblings, leaving the choice partly to inference.

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