Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

get_sprite_metadata

Read-only

Reads a sprite's typed key/value metadata (Properties) to inspect custom properties stored in Aseprite.

Instructions

Read the sprite's typed key/value metadata (Properties).

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

Input Schema

NameRequiredDescriptionDefault
fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes the safety profile, so the bar is lower. The description adds useful scope information — that the data is a typed key/value map called 'Properties' — but says nothing about behavior when a sprite has no metadata, what the return shape looks like, or which sprite is read by default.

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?

A single tight sentence with the resource front-loaded and no filler. It is efficient, though the terseness comes at the cost of the missing usage and parameter detail noted elsewhere.

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

Completeness3/5

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

For a simple read tool with an explicit readOnlyHint and no output schema, the description covers the what but leaves two real gaps: which sprite is targeted when 'file' is omitted, and what the returned key/value structure looks like. Adequate but not complete for correct invocation.

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 parameter 'file' has 0% schema description coverage, and the description does not mention it at all. Critically, it never explains whether omitting the optional parameter falls back to the active sprite, which is the key semantic an agent needs.

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 pairs a specific verb ('Read') with a specific resource ('the sprite's typed key/value metadata (Properties)'), and the parenthetical clarifies what 'metadata' means in this domain. It implicitly contrasts with the sibling set_sprite_metadata, but never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus get_sprite_info or get_pixel-style readers, and no mention of prerequisites such as whether a sprite must be open/active first. The agent must infer the use case entirely from the name.

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