Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

export_unity_sprite

Exports a horizontal sprite sheet and writes a Unity .meta file with named Multiple-mode sprites pre-sliced per frame, removing manual Sprite Editor slicing for Unity 2021.3+/6.

Instructions

Export a horizontal sprite sheet AND write the Unity .meta beside it, pre-sliced into named Multiple-mode sprites (one per frame) — one action, no manual Sprite Editor pass. alignment is one of center, top_left, top, top_right, left, right, bottom_left, bottom, bottom_right, custom; custom uses pivot_x/pivot_y (0..1, 0,0 = bottom left). Targets Unity 2021.3+/6. 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": {
      "png_path": "<png_path>"
    },
    "name": "export_unity_sprite"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
pivot_xNo
pivot_yNo
png_pathYes
alignmentNocustom
pixels_per_unitNo

Output Schema

NameRequiredDescriptionDefault
pngNo
guidNo
metaNo
modeNo
framesNo
spritesNo
alignmentNo
frame_sizeNo
png_existsNo
sheet_sizeNo
texture_sizeNo
pixels_per_unitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only supply destructiveHint=false, so the description carries most of the behavioral load and does add real context: it discloses that a ``.meta`` file is written beside the sheet as a side effect, that slicing is baked in as named Multiple-mode sprites, and that it targets Unity 2021.3+/6. It stops short of saying whether an existing ``.meta`` is overwritten or how collisions are handled, which matters for a write tool.

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?

The core action and its side effect are front-loaded in the first sentence, with parameter details and the Unity version note following. The backtick-heavy formatting and the trailing 'Headless: pass ``file``' fragment are slightly clipped, but no sentence is filler.

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?

An output schema exists, so return values need not be described. However, for a six-parameter tool that writes a file, the description omits the relationship between ``png_path`` and ``file``, the meaning of ``pixels_per_unit``, and overwrite behavior for an existing ``.meta`` — gaps an agent would need to fill before invoking confidently.

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%, so the description must compensate, and it partially does: it enumerates the valid ``alignment`` values (including 'custom') even though the schema declares no enum, and explains that custom uses ``pivot_x``/``pivot_y`` in 0..1 with 0,0 at bottom left. It leaves ``png_path``, ``pixels_per_unit`` and the precise role of ``file`` unexplained beyond a one-word headless hint, so coverage remains partial.

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 names a specific verb and resource: export a horizontal sprite sheet and write the Unity ``.meta`` file pre-sliced into Multiple-mode sprites. That is far more specific than the bare name and makes the dual output (image + meta) explicit. It does not explicitly differentiate itself from close siblings like export_unity_slices or export_spritesheet, which keeps it at 4 rather than 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?

Useful context is implied — 'one action, no manual Sprite Editor pass' tells the agent this replaces the manual slicing workflow, and 'Headless: pass ``file``' hints at a non-interactive mode. But there is no explicit statement of when to choose this over export_unity_slices or export_spritesheet, and no prerequisites or exclusions are 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