Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

batch_apply_palette

Applies a preset or explicit palette to every .aseprite file in a folder, exports converted sprites, and continues past per-file errors for unattended batch palette locking.

Instructions

Palette-lock every .aseprite in folder: snap each sprite (first frame, alpha preserved) to a palette and export images to out_dir. Give a preset (gameboy/pico8/cga) or an explicit palette list of #rrggbb. Non-destructive; continues past per-file errors. Headless.

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

Input Schema

NameRequiredDescriptionDefault
fileNo
folderYes
formatNopng
presetNo
out_dirNo
paletteNo
recursiveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior3/5

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

Only a title annotation exists, so the description carries the full behavioral burden. It does disclose meaningful traits: non-destructive writes, continues past per-file errors, headless execution, only the first frame is processed, alpha is preserved. However it leaves unspecified what happens when out_dir is null, whether existing files are overwritten, and how the undocumented 'file' parameter interacts with 'folder'.

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 action and scope open the description, options follow, and behavioral guarantees close it. Every sentence carries distinct information with no padding, and the parenthetical about first-frame/alpha is efficiently compressed.

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 batch mutation tool with no output schema and no annotations, the description covers the essential shape of the operation and its two main safety/behavior properties. Gaps remain around the 'file' and 'recursive' parameters and default output behavior, but the description is broadly sufficient to invoke the tool correctly.

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% across 7 parameters, so the description must compensate. It usefully explains folder, out_dir, preset (with the accepted values gameboy/pico8/cga) and palette (#rrggbb list), but 'file', 'recursive' and 'format' are never mentioned, leaving nearly half the parameters with no semantics anywhere.

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 ('Palette-lock every .aseprite'), a precise resource (folder of .aseprite files), and the two-part effect (snap to palette, export to out_dir). The batch scope ('every .aseprite in folder') makes it distinguishable from single-file siblings like apply_preset_palette without needing their definitions.

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?

Gives useful selection guidance among mutually exclusive options ('Give a preset ... or an explicit palette list of #rrggbb'), which is the main decision an agent faces here. But it never says when to use this batch tool versus batch_export or the single-file palette appliers, and gives no prerequisites or failure conditions for the folder argument.

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