Skip to main content
Glama

Ase Select All

ase_select_all

Selects the entire cel in Aseprite for the specified sprite, layer, and frame, enabling full-cel edits or transformations.

Instructions

Select the whole cel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frameNo
layerNo
sprite_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.6/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Select the whole cel' without explaining whether this replaces the existing selection, is destructive, or what the output represents. This is insufficient for a tool that modifies sprite state.

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

Conciseness2/5

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

The description is a single sentence, which is concise, but it is under-specified rather than efficiently informative. It omits essential details about the operation, parameters, and behavior, so brevity does not serve the agent's needs.

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

Completeness1/5

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

For a tool with three parameters, no annotations, and an ambiguous domain term, the description is severely incomplete. It fails to define 'cel', explain parameter roles, or disclose behavioral effects, leaving the agent without the information needed for correct invocation.

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 schema has 0% description coverage, and the description does not mention any of the three parameters (sprite_path, frame, layer). The agent receives no help understanding how these parameters affect the selection, so it cannot correctly compose the arguments.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb ('Select') and a specific resource ('the whole cel'), but 'cel' is an undefined term that an agent may not recognize. It does not differentiate from sibling selection tools like ase_select_rectangle or ase_deselect, leaving ambiguity about the exact scope of the operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or scenarios where this tool is preferred, leaving the agent to guess.

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