Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

set_sprite_metadata

Attach typed key/value metadata to a sprite and store it in the .aseprite file, enabling provenance tracking and pipeline state in one undoable edit.

Instructions

Attach typed key/value metadata to the sprite (Aseprite's Properties system — stored in the .aseprite file itself). Values may be strings, numbers, or booleans. Useful for provenance ("generated_by", spec IDs) and pipeline state. One undo step.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "entries": "<entries>"
    },
    "name": "set_sprite_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
entriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations carry only a title, so the description bears the full disclosure burden. It does add real value by noting persistence in the .aseprite file and that the operation is 'One undo step', but it never explains overwrite/merge semantics for existing keys or whether the file must be saved afterward.

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?

Four short sentences, front-loaded with the core action, then storage location, then value types, then use cases, and closing with the terse undo note. Nothing is redundant.

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 mutation tool with no annotations, no output schema, and a free-form nested object parameter, the description covers purpose, storage, value types, and undoability. It still omits merge-vs-replace behavior and the meaning of the `file` parameter, which an agent needs before calling it safely.

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 compensate. It does clarify the shape of `entries` (keys mapped to strings, numbers, or booleans), which the bare `additionalProperties: true` schema does not, but it says nothing at all about the optional `file` parameter, leaving a meaningful gap.

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 verb and resource ('attach typed key/value metadata to the sprite') and names the underlying system (Aseprite Properties) plus where it persists (the .aseprite file itself). This makes it clearly distinguishable from get_sprite_metadata and from unrelated set_* tools in the sibling list.

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?

Gives concrete motivating use cases ('generated_by', spec IDs, pipeline state), which is better than nothing, but offers no when-not guidance and no alternatives. It also leaves a critical usage question unanswered: whether entries are merged with existing metadata or replace it entirely.

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