Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

import_spritesheet

Slice a sheet PNG into animation frames by reading row-major cells at a specified frame size, placing them on an imported layer and adding frames as needed.

Instructions

Slice a sheet PNG into animation frames: cells are read row-major at the given frame size onto a new "imported" layer, adding frames as needed. The sheet's dimensions must be exact multiples of the frame size. One undo step. Headless: pass file (the target sprite).

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": {
      "sheet_path": "<sheet_path>",
      "frame_width": "<frame_width>",
      "frame_height": "<frame_height>"
    },
    "name": "import_spritesheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
sheet_pathYes
frame_widthYes
frame_heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations supply only a title, so the description carries the full burden and does it well: row-major cell order, output onto a new "imported" layer, frames added as needed, the exact-multiple dimension precondition, and single undo-step granularity. It stops short of saying what happens when the multiple-of-frame-size precondition fails (error type) or whether existing frames are overwritten.

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 dense sentences, front-loaded with the action and followed by the precondition, side effects, and undo semantics; no filler. The internal-quote formatting around "imported" is slightly awkward but not wasteful.

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 four-parameter mutation tool with no annotations and no output schema, the description covers preconditions, side effects, layer creation, and undo behavior. Only failure-mode behavior and any return indication are left unaddressed.

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%, so every parameter is undocumented in structured fields. The description partially compensates: "given frame size" maps to frame_width/frame_height, `file` is explained as the target sprite, and sheet_path is implied by "sheet PNG", but it adds no format or resolution detail for sheet_path and does not clarify why file is optional/default null.

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 ("Slice a sheet PNG into animation frames") plus the destination layer, which implicitly separates it from import_image_as_layer and export_spritesheet. It never names a sibling explicitly, so the differentiation is inferred rather than stated.

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?

Usage context is implied by the import workflow and the "Headless: pass file" note, but there is no explicit when-to-use or when-not-to-use guidance, and no named alternative such as import_image_as_layer for single images.

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