Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

create_slice

Creates a named atlas region at a specified rectangle for export as Unity sprites in one undo step, with optional headless file targeting.

Instructions

Create a named slice (atlas region) at the given rectangle. Slices become Unity sprites via export_unity_slices. One undo step. 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": {
      "name": "<name>",
      "x": "<x>",
      "y": "<y>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "create_slice"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
fileNo
nameYes
widthYes
heightYes

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 supply only a title, so the description carries the burden, and it does disclose two non-obvious traits: the operation is a single undo step and headless callers must supply `file`. It leaves out failure behavior (invalid rectangles, name collisions) and what the return value is, which keeps it below a 5.

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 short sentences, front-loaded with the core action, with the export relationship and the undo/headless notes following in priority order. No filler, though the terse "Headless: pass ``file``" phrasing is slightly cryptic without a supporting clause.

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 mutation tool with no output schema and zero schema description coverage, the description covers purpose, undo semantics, and the headless flag, which is respectable. It is still thin on coordinate semantics for the four geometry parameters and on what identifier or result comes back from a created slice.

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 the description must compensate; it maps the required set by naming the slice, the rectangle, and the `file` parameter for headless mode. However it adds no meaning about coordinate convention (origin, top-left vs center), units, or whether width/height are pixels, so the four geometry params remain under-explained.

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?

Uses a specific verb+resource ("Create a named slice") and clarifies what a slice is ("atlas region") plus its downstream role ("become Unity sprites via export_unity_slices"), which separates it from create_sprite and the export step. It stops short of explicitly contrasting with the sibling slice tools like delete_slice or set_slice_center, but the create/name/rectangle framing is 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?

Gives a clear workflow cue by naming export_unity_slices as the follow-on step and a conditional for headless operation ("pass file"). There is no explicit when-not guidance or mention of prerequisites such as what happens with overlapping or out-of-bounds regions, so usage context is present but not complete.

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