Aseprite-MCP

by iborymagic

Overview Schema Source Related Servers Discussions Admin

TypeScript

auto_crop_transparent

Automatically remove empty transparent borders from sprites to optimize canvas size and reduce file size.

Instructions

Automatically crops empty transparent borders of the sprite

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": {
      "saveOutput": "<saveOutput>",
      "inputFile": "<inputFile>"
    },
    "name": "auto_crop_transparent"
  }
}

Input Schema

Name	Required	Description	Default
`inputFile`	Yes
`saveOutput`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Jul 5, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations provided; description does not disclose traits like whether modification is in-place, effect on non-transparent areas, or side effects.

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?

Single sentence is concise but lacks structure; no front-loading of key information like parameter details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with two required parameters and no output schema, the description inadequately explains the operation, parameters, and return behavior.

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 coverage is 0% and description does not explain parameters (inputFile, saveOutput) at all, failing to add meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (crops), resource (sprite), and specific scope (empty transparent borders). It is distinct from sibling tools which focus on other operations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, and no context about prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.