Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

get_sprite_info

Read-only

Inspect the active sprite's size, color mode, and layer/frame/tag lists; pass a .aseprite file to read the same details headlessly.

Instructions

Get the active sprite's size, color mode, and layer/frame/tag lists. Headless: pass file (the .aseprite to inspect).

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

Input Schema

NameRequiredDescriptionDefault
fileNo

Output Schema

NameRequiredDescriptionDefault
tagsNo
widthNo
framesNo
heightNo
layersNo
filenameNo
colorModeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and an output schema exists, so the safety and return-shape burden is largely carried elsewhere. The description confirms it targets the 'active' sprite and adds the headless file-mode behavior, but it doesn't say what happens when no sprite is active or how 'active' is determined.

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

Conciseness4/5

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

Two sentences, front-loaded with the primary outcome and followed by the conditional headless usage note. No filler; the second line is clearly framed as an extra case rather than the default path.

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?

The tool is simple (one optional param, read-only, output schema present), so the description covers what's needed: what it returns and how to point it at a file headlessly. The only gap is guidance on resolving the 'active' sprite in non-headless context.

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 description coverage is 0%, so the description must carry the single 'file' parameter, and it does clarify that it should be a path to the .aseprite and that it's used specifically in headless mode. That's meaningful but minimal — no format example, absolute vs relative path, or default behavior when omitted.

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 names a specific verb and resource ('Get the active sprite's...') and enumerates the returned data (size, color mode, layer/frame/tag lists), so an agent knows exactly what it retrieves. It does not differentiate itself from plausible siblings like get_sprite_metadata or describe_sprite, which keeps it 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?

It provides one concrete usage rule — in headless mode pass 'file' with the .aseprite to inspect — which is genuinely actionable. It gives no guidance on when to prefer this over get_sprite_metadata or describe_sprite, and no exclusion cases.

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