Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

set_slice_pivot

Idempotent

Set a slice's pixel pivot point relative to its top-left corner so the offset exports into Unity .meta files via export_unity_slices. Use it to align sprite anchors before asset export.

Instructions

Set a slice's pivot point, in pixels relative to the slice's top-left. This pivot is exported into the Unity .meta by 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>",
      "pivot_x": "<pivot_x>",
      "pivot_y": "<pivot_y>"
    },
    "name": "set_slice_pivot"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
nameYes
pivot_xYes
pivot_yYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.9/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing the undo cost ('One undo step') and the export side effect on the Unity .meta file — neither of which is captured by idempotentHint. Coordinate origin is also specified. It does not mention required editor state or what happens if the named slice is absent, so it is strong but not exhaustive.

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 short sentences, front-loaded with the core action and coordinate frame, with the export, undo, and headless notes following in priority order. The telegraphic 'Headless: pass ``file``' is dense but borderline cryptic rather than wasteful.

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 4-parameter mutation with no output schema and thin annotations, the description covers the important invisible behavior: coordinate frame, undo cost, and downstream export coupling. The main residual gap is identifying what 'name' refers to and any precondition that the slice must already exist.

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 carries the burden: it establishes the units and origin for pivot_x/pivot_y and the headless condition for 'file'. However, the 'name' parameter is never explained (slice identifier? file?), and the required integer typing and valid ranges for the pivot coordinates are left undocumented.

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 pivot point') plus the coordinate frame ('in pixels relative to the slice's top-left'), which is more than the name alone conveys. It also ties the value to a downstream consumer (export_unity_slices), but never distinguishes this from the obvious sibling set_slice_center, leaving the pivot-vs-center choice to inference.

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?

Gives clear context for when this matters (the pivot feeds the Unity .meta export via export_unity_slices) and a conditional operating mode ('Headless: pass file'). It stops short of naming an alternative or stating exclusions, but an agent knows the scenario in which to reach for it.

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