Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

split_sheet

Split a grid-based character sheet into individual pixel-art pose sprites at one scale and shared palette, then tag each sprite for selection. Use it to keep animation poses consistent.

Instructions

Cut a character sheet (poses in a columns x rows grid) into one pixel-art sprite per pose, all at the same scale and on ONE shared palette of colors colours (or palette), so the poses stay consistent with each other. Each cell is shrunk to width x height (the cell's aspect by default), its background cleared and the bits of neighbouring poses dropped. Each sprite gets a tag named from names (row by row; "pose_1"... by default), so pin_sprite(tag=...) can pick it. Live: opens the sprites in the editor. Headless: writes <out_dir>/<name>.aseprite.

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>",
      "columns": "<columns>",
      "rows": "<rows>",
      "width": "<width>"
    },
    "name": "split_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
namesNo
widthYes
colorsNo
ditherNonone
heightNo
columnsYes
out_dirNo
paletteNo
image_pathYes
layer_nameNoArt
clear_edgesNo
remove_backgroundNo

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?

Annotations supply only `openWorldHint`, so the description carries most of the burden and does so well: it discloses the shared palette/scale constraint, per-cell resizing with aspect-preserving default height, background clearing, neighbour-fragment removal, and the two output modes. It does not say whether existing files in `out_dir` are overwritten, which is the one meaningful behavioral gap.

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?

Four sentences, front-loaded with the core operation and ending with the live/headless distinction, with no filler. There is mild redundancy in stating the shared scale/palette and then restating that poses stay consistent with each other.

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 13-parameter tool with no output schema and minimal annotations, the description covers the essential mechanics and the file output path. It still leaves four parameters (`dither`, `layer_name`, `clear_edges`, `image_path`) unexplained and does not address overwrite behavior in `out_dir`, so it is adequate but not fully complete.

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 13 parameters, so the description must compensate, and it covers roughly half: `columns`/`rows` grid, `colors`/`palette` sharing, `width`/`height` with default aspect, `names` row-by-row with a `pose_1` default, and `out_dir`. It says nothing about `dither`, `layer_name`, `clear_edges`, or `image_path`, so several parameters remain undocumented in both places.

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 gives a specific verb and resource: cut a character sheet of `columns` x `rows` poses into one sprite per pose. It never differentiates itself from the sibling `split_into_layers`, which is the nearest-looking alternative, 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 Guidelines4/5

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

Usage context is clear: it is for grid-laid-out character sheets, and it spells out the two execution modes (Live opens sprites in the editor, Headless writes `<out_dir>/<name>.aseprite`). It offers no exclusions or named alternatives, so it does not reach the explicit when-not guidance of a 5.

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