Skip to main content
Glama
Sign In
aseprite-mcp

aseprite-mcp

by shin2344234
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_cels

Read-only

List cels (layer/frame pairs with images), including bounds, opacity, z-index, and data, filtered by layer and frames to inspect or target specific animation cells.

Instructions

Lists cels (layer/frame pairs with images) with bounds, opacity, z-index and data, filtered by layer and frames.

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

Input Schema

NameRequiredDescriptionDefault
toNoLast frame of a range
tagNoUse the frames of this tag
fromNoFirst frame of a range
frameNo1-based frame number. Defaults to the active frame (or 1).
layerNoLayer name, 'Group/Child' path, or 1-based index from get_sprite_info. Defaults to the active layer.
framesNo'all' or a list of frame numbers
spriteNoFile path, open tab title, or sprite id. Defaults to the active sprite (live). Batch mode needs a file path.
backendNoauto (default): live Aseprite if connected, else headless batch

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuine value beyond that by enumerating the returned fields (bounds, opacity, z-index, data), which matters because there is no output schema, and by stating that results are filtered by layer and frames.

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?

A single front-loaded sentence that names the operation, defines the resource, lists the returned data, and states the filtering dimension with zero filler.

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

Completeness4/5

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

For an 8-parameter read tool with no output schema, the description supplies the return shape and the filtering scope, while the schema carries all parameter defaults and constraints. It does not discuss batch-mode caveats or volume/pagination limits, so it is solid but not exhaustive.

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

Parameters3/5

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

Schema coverage is 100%, and the schema already documents defaults, allowed values, and formats for all 8 parameters. The description's 'filtered by layer and frames' merely restates a subset of those parameters without adding syntax or format detail, so baseline 3 is correct.

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 ('Lists') and resource ('cels'), and defines a cel as a layer/frame pair with images, which clearly separates it from the sibling mutators update_cel, delete_cel, copy_cel and link_cels. It does not name a sibling explicitly, so it stops short of a 5.

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 read-only listing intent is implied by 'Lists' and the annotations, but the description gives no explicit when-to-use guidance, no exclusions, and does not point to alternatives such as get_pixels or get_sprite_info. Usage must be inferred.

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