Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

select_all

Idempotent

Selects the entire canvas in Aseprite so you can edit, transform, or export the whole image at once. Use it before operations that must apply to every pixel.

Instructions

Select the whole canvas.

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

Input Schema

NameRequiredDescriptionDefault
fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations only supply idempotentHint and a title, so the description carries the rest of the burden and does not deliver. It never says whether an existing selection is replaced or extended, whether the optional file argument changes the target, or what state results after the call. For a selection-mutating operation with sparse annotations, this leaves meaningful behavior undisclosed.

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?

One short, front-loaded sentence with zero filler. It is terse to the point of under-specification, but nothing in it is wasted.

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?

No output schema, no annotation coverage beyond idempotency, and an undocumented parameter. The description does not do enough to make the tool safely callable without opening the schema and guessing at "file".

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% for the single optional "file" parameter, so the description must compensate and does not. "Whole canvas" implies a target but never explains what "file" means or when to supply it rather than omit it.

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 object: "Select the whole canvas." It is clear what the tool does and distinguishes itself from finer-grained selection siblings like select_rectangle or select_layer by covering the entire canvas, though it does not name any sibling explicitly.

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?

There is no when-to-use or when-not-to-use guidance at all. The agent must infer from the name alone that this is the bulk-select shortcut versus the many narrower select_* siblings, and nothing clarifies that relationship.

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