Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

erase_area

Destructive

Erases pixels to transparent in an explicit rectangle for headless edits or in the current selection, including non-rectangular live selections, as one undo step.

Instructions

Erase pixels to transparent. Pass an explicit rect (works everywhere, including headless), or pass nothing to erase the current selection — including non-rectangular ones (live editor). One undo step.

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": "erase_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
fileNo
widthNo
heightNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, but the description adds genuinely new behavioral facts: the operation is a single undo step, and the no-argument selection mode only works in the live editor while headless requires an explicit rect. It still omits what happens to partially-specified rectangles and what the 'file' parameter targets.

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?

Two compact sentences, front-loaded with the core action, followed by the mode guidance and the undo note. No filler or redundancy.

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 zero-required-parameter destructive tool with no output schema, the description covers the main invocation modes, environment constraint (headless vs. live editor), and undo semantics. The unexplained 'file' parameter and undefined behavior for partial rectangle arguments keep it from being fully complete.

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 carry the parameter burden. It implies that the numeric parameters form a rectangle and explains the omit-all case, but never maps x/y/width/height explicitly and never mentions the 'file' parameter at all.

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 ('Erase pixels to transparent') plus the two operating modes (explicit rect vs. current selection). It does not name any sibling tool (e.g., fill_area, undo), so differentiation is by concept rather than by explicit routing.

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 conditional guidance: pass an explicit rect for 'works everywhere, including headless', or pass nothing to operate on the current selection in the live editor. It does not address alternatives to erasing (fill, undo) or prerequisites, so it stops short of full when/when-not routing.

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