Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

describe_sprite

Read-only

Summarize the active Aseprite sprite in one call, including size, color mode, layers, frames, tags, slices, palette, and selection, to inspect canvas state before editing or exporting.

Instructions

Summarize the active sprite in one call: size, color mode, the layer tree with visibility and blend modes, frame timing, tags, slices, palette, the selection, and what's active. Frame durations and palette colors stop at 64 entries; count always gives the full number.

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

Input Schema

NameRequiredDescriptionDefault
fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior4/5

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

With readOnlyHint already declaring safety, the description still adds real behavioral value: it discloses truncation limits (frame durations and palette colors capped at 64 entries) and that ``count`` reports the true totals. It also scopes the operation to the active sprite. It stops short of noting cost/size of the returned payload.

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?

One tight sentence enumerates the payload scope, followed by a short caveat about the 64-entry caps. Purpose is front-loaded and no sentence is 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?

There is no output schema, so the description carries the burden of describing return content, and it does so by enumerating the major sections plus truncation semantics. Worded correctly, but the shape/format of the returned summary and the meaning of `file` remain undocumented.

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?

The single optional `file` parameter has 0% schema description coverage, and the description never mentions it — it only speaks of the "active sprite", leaving unclear whether `file` overrides the active target or what form it takes. With only one parameter this is a modest but real gap that the description should have closed.

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?

The description gives a specific verb and resource ("Summarize the active sprite") and enumerates the content domains covered (layer tree, frame timing, tags, slices, palette, selection). It is clear what the tool does, but it never distinguishes itself from close siblings like get_sprite_info or get_sprite_metadata, which an agent would reasonably confuse it with.

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?

"in one call" implies this is the comprehensive single-shot alternative to making several narrower queries, which is useful implied usage. However, there is no explicit statement of when to prefer it over get_sprite_info/get_sprite_metadata or any exclusion, so the agent must infer the routing.

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