Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

export_spritesheet

Pack all sprite frames into one sprite-sheet image and optionally write a JSON atlas, using row, column, or packed layouts for game-asset export.

Instructions

Pack all frames into a single sprite-sheet image (optionally writing a JSON atlas to data_path). sheet_type is rows | columns | horizontal | vertical | packed. Does not modify the sprite. Headless: pass file.

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

Input Schema

NameRequiredDescriptionDefault
fileNo
out_pathYes
data_pathNo
sheet_typeNorows

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 already declare destructiveHint=false and openWorldHint=true, and the description reinforces that with 'Does not modify the sprite' while adding two facts the annotations cannot convey: an optional JSON atlas is written as a side effect to ``data_path``, and headless invocation requires ``file``. It does not say what happens when ``out_path`` already exists, which is the main remaining behavioral unknown.

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 tight sentences, front-loaded with the primary action before the optional atlas and parameter notes. The telegraphic 'Headless: pass ``file``' is efficient but slightly clipped compared to the rest of the prose.

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, non-destructive export with no output schema, the definition covers the output artifact, the optional sidecar file, the layout modes, and the headless requirement. Missing only overwrite semantics and confirmation of what the tool returns or writes to disk.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and largely meets it: it explains ``data_path`` as an optional JSON atlas destination, documents ``file`` as the headless handle, and enumerates ``sheet_type`` values (rows | columns | horizontal | vertical | packed) that the schema does not constrain via enum. Only ``out_path`` is left implicit rather than explicitly named.

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 result: 'Pack all frames into a single sprite-sheet image', which distinguishes it from the animation/layer/tileset exporters in the sibling list. It stops short of naming which sibling to prefer when the goal is a game-engine-specific format, but the resource and output shape are unambiguous.

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?

'Headless: pass ``file``' is a real usage condition, and 'Does not modify the sprite' sets expectations. However, there is no guidance on when to choose this over export_animation, export_layers, or the engine-specific exporters, so the agent must infer the choice from tool names alone.

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