Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

set_slice_center

Idempotent

Defines a named slice's 9-patch stretchable center rectangle so UI graphics can scale without distorting borders. Use it to set the center region relative to the slice.

Instructions

Set a slice's 9-patch stretchable center rectangle (relative to the slice). 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": "set_slice_center"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
fileNo
nameYes
widthYes
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 only supply idempotentHint and a title, so the description carries most of the burden. It usefully discloses that the operation consumes exactly 'One undo step' and that a ``file`` argument is required in headless mode — both are real behavioral facts an agent cannot get from structured fields. It does not say what happens if the named slice is missing.

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?

Two tight sentences, front-loaded with the effect and followed by the two operational caveats. Nothing is wasted, though the terseness leaves the parameter list entirely unexplained.

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 five-required-parameter mutation with no output schema and zero schema descriptions, the essentials are covered: what is mutated, the coordinate frame, undo cost, and headless targeting. Error behavior and coordinate units remain gaps.

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: it establishes that x/y/width/height are measured relative to the slice and that ``file`` selects the headless target. It says nothing about units, whether x/y is the top-left of the rectangle, or what ``name`` refers to (a slice name vs. file name).

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: 'Set a slice's 9-patch stretchable center rectangle'. The parenthetical '(relative to the slice)' clarifies the coordinate frame, and 'center' implicitly contrasts with the sibling set_slice_pivot, though that sibling is never named.

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?

There is a conditional usage hint ('Headless: pass ``file``') that tells the agent when to supply the optional parameter, but no guidance on when to use this tool versus set_slice_pivot or other slice tools, and no prerequisites (e.g. slice must already exist).

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