Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

apply_bundled_palette

Applies a bundled Aseprite extension palette by resource ID, such as DB16 or DB32, to recolor pixel art in one undoable step.

Instructions

Apply one of Aseprite's bundled extension palettes by resource ID — e.g. DB16, DB32, ARQ4, EDG16 (availability depends on the installed palette extensions). For gameboy/pico8/cga see apply_preset_palette. One undo step.

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

Input Schema

NameRequiredDescriptionDefault
fileNo
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/5.0
Behavior4/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 burden — and it does disclose two behavioral traits: the operation is reversible in exactly one undo step, and the resource may not exist depending on installed extensions. It does not say which document/sprite is mutated or what happens on an unknown palette name, leaving a gap for a mutation tool with no destructiveHint.

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 short sentences, front-loaded with the action and examples, followed by the exclusion and the undo note. Slight redundancy in restating 'bundled extension palettes' already implied by the name, but nothing wasted overall.

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 simple two-parameter mutating tool with no output schema, the description covers scope, examples, sibling routing, and reversibility. The remaining gaps — the meaning of `file` and failure behavior for unavailable palettes — are minor but real.

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 description coverage is 0%, so the description must compensate. It does clarify that the string identifier is a palette resource ID (not a display name) via examples, but it never mentions the `file` parameter at all, and the schema field is called `name` rather than the ID term used in prose — a small mismatch that could cause wrong values to be passed.

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 (apply a bundled extension palette) and pins down the identifier space with concrete examples (DB16, DB32, ARQ4, EDG16). It also explicitly distinguishes itself from apply_preset_palette, so an agent can route between the two without inspecting schemas.

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

Usage Guidelines5/5

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

Names the alternative tool and the exact condition that selects it: gameboy/pico8/cga palettes belong to apply_preset_palette, everything else bundled goes here. It also warns that availability depends on which palette extensions are installed, which is a real precondition for success.

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