Aseprite-MCP

by iborymagic

Overview Schema Source Related Servers Discussions Admin

TypeScript

get_selection_bounds

Get the bounding rectangle of the active sprite's selection, returning its position and size dimensions.

Instructions

Gets the bounds of the selection in the active 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": {
      "inputFile": "<inputFile>"
    },
    "name": "get_selection_bounds"
  }
}

Input Schema

Name	Required	Description	Default
`inputFile`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Jul 5, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations, the description fails to disclose behaviors such as what happens if there is no selection, error handling, or whether the tool is idempotent. It only implies a read operation.

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?

The description is a single sentence with no wasted words, but it omits critical information about the parameter, making it insufficiently informative.

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?

Given the lack of output schema and zero schema description coverage, the description should provide more context about the return value, parameter format, and edge cases, which it does not.

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?

The sole parameter 'inputFile' is not described in the schema or the description; with 0% schema coverage, the description must explain it but 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?

The description clearly states the tool retrieves the bounds of the selection in the active sprite, distinguishing it from siblings that deal with other sprite properties like frame info or layer lists.

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 is provided on when to use this tool versus alternatives, nor are there any prerequisites or conditions for usage.

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