Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

export_unity_slices

Exports a sprite as a PNG plus a Unity .meta containing one multiple-mode sprite per named slice with its pivot, so Unity imports the atlas already sliced and pivoted.

Instructions

Export the sprite as a single PNG AND write a Unity .meta with one Multiple-mode sprite per named slice, each carrying that slice's pivot — so an atlas laid out with slices imports into Unity already sliced and pivoted. No competitor's Aseprite→Unity path exports pivots. Requires slices (see create_slice / set_slice_pivot). 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_slices"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
png_pathYes
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

B3.2/5.0
Behavior3/5

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

Annotations only declare destructiveHint=false and a title, so the description carries most of the behavioral burden, and it does add real value: it writes a second artifact (.meta), uses Multiple-mode sprites, and per-slice pivots. However, it never says whether an existing .meta/.png is overwritten, where the .meta lands, or what happens if a slice lacks a pivot — material gaps for a file-writing tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is dense and front-loaded with the key behavior, but the sentence 'No competitor's Aseprite→Unity path exports pivots' is pure marketing and earns no place in a tool definition. The prerequisite and headless notes that follow are useful but crammed in italics-style fragments rather than structured.

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 needn't be described, and the core behavior plus prerequisite are covered. Still, for a file-emitting Unity export tool, the meaning of pixels_per_unit and png_path and the overwrite behavior are missing, so an agent could call it correctly on paths but not necessarily with the right intent.

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

Parameters1/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 explain all three parameters; it only addresses 'file' ('Headless: pass ``file``'). png_path (the required output path) and pixels_per_unit — the Unity import scale setting that directly affects import correctness — are never explained in the description or the schema. With two of three parameters entirely undocumented, this is a serious gap.

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 states a specific verb and output set: export the sprite to a single PNG and write a Unity .meta containing one Multiple-mode sprite per named slice with pivots. This clearly separates it from a plain unity sprite export because the slice-count/pivot behavior is spelled out. It stops short of naming the sibling (export_unity_sprite) it contrasts against, so an agent must infer the non-slice alternative.

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?

It gives a hard prerequisite ('Requires slices') and routes the agent to create_slice / set_slice_pivot to satisfy it, plus a headless-mode usage note ('pass ``file``'). There is no explicit when-not-to-use guidance or pointer to the non-slice Unity export alternative, so it's clear context without exclusions.

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