Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

load_palette

Replace a sprite's palette by loading a palette file (.gpl, .pal, .ase, or .png strip) in one undoable step.

Instructions

Replace the sprite's palette from a palette file (.gpl, .pal, .ase, .png strip — anything Aseprite reads). 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": {
      "path": "<path>"
    },
    "name": "load_palette"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3/5.0
Behavior2/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 add one valuable trait — 'One undo step' — plus the accepted format set, but says nothing about whether existing colors are discarded or remapped, whether the file is read-only, or what happens on an unreadable/unsupported file.

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?

Two compact sentences, front-loaded with the action and followed by the format list and undo note. Every clause earns its place; the parenthetical is dense but useful rather than padding.

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 simple two-parameter mutation with no output schema, the description covers formats and undoability but omits the fate of the sprite's pixels/colors on replacement and the path-vs-file distinction. Adequate, not complete.

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% and the description adds no per-parameter meaning. With two similarly-named inputs (`path` required, `file` optional and nullable) the description's 'palette file' wording does not clarify which parameter is which or why two exist, leaving real ambiguity.

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 — 'Replace the sprite's palette from a palette file' — and enumerates accepted formats (.gpl, .pal, .ase, .png strip). It does not explicitly differentiate itself from siblings like set_palette or apply_preset_palette, so it stops 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 'from a palette file' implies the use case (you have a palette file on disk rather than a bundled preset), but there is no explicit when-to-use, no exclusion of alternatives, and no statement about prerequisites. Guidance is inferable rather than stated.

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