Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

autocrop_sprite

Trims transparent borders and shrinks the canvas to the union of visible content across all layers and frames, returning old and new size; errors if the sprite is fully transparent.

Instructions

Trim transparent borders: shrink the canvas to the union of visible content across all layers and frames (Sprite > Trim). Errors if the sprite is fully transparent. Returns the old and new size. One undo step. Headless: pass file.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "autocrop_sprite"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

With only a title annotation, the description carries the behavioral burden and does well: it discloses the failure mode (fully transparent sprite), the return payload (old and new size), and the side effect on history (one undo step). It does not say what happens to frame/layer structure or whether the operation is reversible beyond the single undo.

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

Conciseness5/5

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

Five short clauses, each carrying distinct information: what is trimmed, the failure case, the return value, the undo cost, and the headless parameter. No filler and the core action is front-loaded.

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 single-parameter mutation with no output schema, the description covers purpose, error condition, return shape, undo cost, and the headless path. The only real gap is not stating which sprite is operated on when 'file' is omitted.

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% for the single 'file' parameter, but the description compensates partially by explaining that it is the headless-mode entry point. It still leaves the expected format (path? file handle?) unstated, so meaning is added but not fully.

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: 'Trim transparent borders' / 'shrink the canvas to the union of visible content across all layers and frames', and anchors it to the app menu path (Sprite > Trim). It does not explicitly say how it differs from the sibling crop_sprite or resize_sprite, so an agent must infer that this is the automatic version.

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?

Usage context is implied by the trim semantics and the 'Errors if the sprite is fully transparent' precondition, but there is no explicit when-to-use-this-vs-crop_sprite guidance and no statement of which sprite is targeted by default (only the headless 'file' escape hatch).

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