Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

select_ellipse

Idempotent

Creates an elliptical selection inside a specified rectangle and can replace, add to, or subtract from the current selection for targeted pixel-art edits.

Instructions

Select an ellipse inscribed in the given rectangle. mode is replace (default), add, or subtract against the current selection.

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_ellipse"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
fileNo
modeNoreplace
widthYes
heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations only supply idempotentHint=true and a title, so the description carries most of the burden. It does add real behavioral value by explaining that mode operates 'against the current selection' with replace as the default, meaning a call without mode discards prior selection. It says nothing about coordinate origin, units, or whether selection affects the active layer, which leaves meaningful behavioral gaps.

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 tight sentences with zero filler: the geometric intent comes first and the mode options follow. Every clause adds information an agent needs.

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

Completeness3/5

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

With no output schema the description should cover a bit more, but for a simple selection tool it is close to sufficient. The main shortfalls are the entirely undocumented 'file' parameter and the undefined coordinate/corner convention, both of which matter for producing a correct call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across six parameters, so the description must compensate and largely does not. Only 'mode' is explained (allowed values and default); x, y, width, height are only implied to be the bounding rectangle, with no statement of whether x/y is the top-left corner or the origin convention, and the 'file' parameter is never mentioned 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 ('Select an ellipse inscribed in the given rectangle'), which is distinguishable from a rectangle selection or a draw operation. It stops short of naming the sibling it differs from (e.g. select_rectangle, draw_ellipse), so the differentiation is inferable rather than explicit.

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?

The mode semantics ('replace', 'add', 'subtract' against the current selection) implicitly tell the agent how to combine selections, which is useful usage context. However, there is no explicit guidance on when to use this tool versus draw_ellipse or select_rectangle, and no preconditions such as an active document or existing selection.

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