Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

list_layers

Read-only

Retrieves a complete Aseprite layer tree, including nested group layers, stack order, visibility, and opacity, so you can inspect or edit every layer in a sprite.

Instructions

The full layer tree, top of stack first: name, path, kind (image/group/tilemap), visibility, and opacity — including layers nested in groups (which get_sprite_info lists only at the top level).

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

Input Schema

NameRequiredDescriptionDefault
fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description is free to spend its words on what the agent actually needs: the shape of the returned data, the ordering guarantee, and the nesting depth included. It adds genuine value beyond the annotation, though it says nothing about how a missing/invalid file is handled or what an empty layer stack looks like.

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 sentence that front-loads the resource, then the per-entry fields, then the distinguishing parenthetical. Nothing is redundant and every clause carries information the agent needs.

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?

With no output schema, the description correctly compensates by enumerating the returned fields and their order. The only real gap is the unexplained `file` parameter; for a low-complexity, read-only listing tool this is otherwise sufficient to call correctly.

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?

There is one optional `file` parameter with 0% schema description coverage and a null default, and the description never mentions it — no indication of what file it targets or what happens when omitted (presumably the active document). The otherwise thorough return-field explanation partially offsets this, so it lands at baseline rather than below.

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

Purpose5/5

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

States a specific resource (the layer tree) and enumerates exactly what each entry contains — name, path, kind, visibility, opacity — while noting ordering ('top of stack first'). It also contrasts itself against get_sprite_info's top-level-only behavior, so an agent can distinguish the two without opening either schema.

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?

The parenthetical clarifies that this tool reaches nested group layers while get_sprite_info does not, which is effective routing guidance to a real decision point. It stops short of an explicit 'use this when / don't use this when' statement, so it falls just short of the top band.

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