Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

list_sprites

Read-only

Lists every open Aseprite document with filename, size, frame/layer counts, tags, unsaved status, active document, and pinned edit target so you can confirm where edits apply.

Instructions

Live editor only: list every open document — filename (or "(unsaved)"), size, frame/layer counts, tags, unsaved-changes flag, which one is active in the editor, and which one Claude's edits go to (pinned).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/5.0
Behavior4/5

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

Read-only safety is already declared in annotations, but the description adds context annotations do not: the live-editor-only restriction, the full shape of what is reported, and the 'pinned' concept telling the agent which document Claude's edits will land in. It stops short of describing ordering, empty-state behavior, or size units.

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: scope constraint first, then a compact dash-delimited enumeration of return fields. Every clause carries information and there is no filler or repetition.

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 and no parameters, the description carries the return-value burden and does so by enumerating the reported fields, which is exactly what an agent needs. Minor gaps remain — ordering, size units, and what happens outside the live editor — but nothing essential to calling it correctly is absent.

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

Parameters4/5

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

The tool takes zero parameters and the description does not invent any, which is correct. The schema has nothing to explain, so the zero-parameter baseline applies; no additional parameter meaning is needed or missing.

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?

Names a specific verb (list) and resource (every open document / sprite), and the enumerated return fields — filename, size, frame/layer counts, tags — make clear this is the file-level listing rather than a sub-resource like layers, tags or slices. The '(unsaved)' and 'pinned' notes further pin down what a 'document' means here.

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?

'Live editor only' is an explicit applicability constraint that tells the agent when this tool is valid and implicitly excludes headless/scripted contexts. It does not, however, name an alternative or state a when-not beyond the environment gate, so no explicit routing guidance is given.

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