Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

select_rectangle

Idempotent

Sets a rectangular selection in the Aseprite canvas using x, y, width, and height coordinates, enabling targeted pixel art edits on the live editor.

Instructions

Set a rectangular selection. Most meaningful on the live editor.

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": {
      "x": "<x>",
      "y": "<y>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "select_rectangle"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
fileNo
widthYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations only declare idempotentHint=true, so the description carries the burden of explaining behavior. It does not say whether an existing selection is replaced, what coordinate space x/y/width/height use, or how the optional file parameter interacts with the live editor. The one sentence about the live editor gestures at a behavioral difference without explaining it.

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?

Two short sentences with no filler and the core action front-loaded. However, the brevity comes at the cost of substance rather than being tight-but-complete, so it earns only a middling score.

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?

A five-parameter geometry tool with no parameter documentation, no output schema, and minimal annotations needs far more from its description. An agent can guess the intent but cannot call it confidently without knowing the coordinate system and selection-replacement semantics.

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?

All five parameters have 0% schema description coverage, so the schema supplies only names and types. The description adds no meaning for x, y, width, height, or file — not even whether coordinates are pixels or tiles, or whether width/height can be negative.

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?

The description names a specific verb and resource ("Set a rectangular selection"), which distinguishes it from draw_rectangle and the select_* siblings by implying it establishes a selection rather than drawing pixels. It stops short of explicitly contrasting itself with select_all or select_ellipse, so an agent still has to infer the boundary.

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?

"Most meaningful on the live editor" is the only contextual hint, and it is vague about what happens off the live editor and why it is less meaningful there. There is no guidance on when to choose this over select_all, select_by_color, select_ellipse, or select_frame.

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