Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

get_selection

Read-only

Checks whether an Aseprite selection exists and returns its bounding rectangle, so live-editor workflows can confirm the selected area before editing.

Instructions

Report whether a selection exists and its bounding rectangle. (Selection is editor-session state — in headless mode it doesn't persist between calls, so this is mainly a live-editor tool.)

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

Input Schema

NameRequiredDescriptionDefault
fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description adds real context beyond it: the return consists of existence plus a bounding rectangle, and the underlying state is ephemeral session state in headless mode. The only shortfall is that the exact shape of the bounding rectangle and the behavior when no selection exists are left implicit.

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

Conciseness4/5

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

Two short sentences, front-loaded with the outcome and followed by a parenthetical caveat. Nothing is padded, though the parenthetical framing makes the important headless limitation read as an aside rather than a first-class condition.

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?

For a one-parameter, read-only tool with no output schema, the description adequately covers what is returned and when it is useful. It is incomplete on the 'file' parameter and on behavior when no selection is present, which an agent would still need to guess.

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?

The single optional 'file' parameter has 0% schema description coverage and the description never mentions it, so an agent gets no idea what it scopes or what null means. With low coverage the description is expected to compensate, and here it does not.

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 ('report whether') and resource ('a selection'), plus the return content (existence and bounding rectangle). An agent can tell this is a read/inspection tool, though the description never explicitly contrasts it with selection-mutating siblings like edit_in_selection or invert_selection.

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 a concrete when-not-to-use signal: selection is editor-session state that does not persist between calls in headless mode, so the tool is mainly for live editors. That is genuine routing guidance, but no alternative tool is named for the headless case, so it stops short of full alternative guidance.

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