Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

set_active_sprite

Idempotent

Activate an open Aseprite document by exact filename or basename so later tools target it, even after another tab is clicked. Live editor only; use pin_sprite for unsaved sprites with duplicate names.

Instructions

Live editor only: make one of the open documents active, found by exact filename or basename match (e.g. "turret.aseprite"). Returns which sprite matched and how. Subsequent tools operate on it, even if the artist clicks another tab. Unsaved sprites share a name: pick those with pin_sprite.

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": {
      "filename": "<filename>"
    },
    "name": "set_active_sprite"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only supply idempotentHint and a title, so the description carries the behavioral load and does it well: it discloses the live-editor restriction, the exact/basename matching rule, that the returned result reports which sprite matched and how, and that the active-sprite state persists against the artist switching tabs.

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 'Live editor only' constraint and the core action, then the matching rule, then the state consequence, then the disambiguation pointer. No 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?

For a single-parameter selection tool with no output schema and minimal annotations, this covers purpose, constraint, matching, and state effects. The only omission is failure behavior when the filename matches nothing or matches more than one open document.

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 coverage is 0%, so the description must compensate for the single filename parameter. It adds real meaning with the example "turret.aseprite" and the exact-vs-basename matching rule, but leaves unresolved what happens on no match, on multiple matches, or whether matching is case-sensitive.

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 — make an open document the active sprite — and pins down the lookup semantics (exact filename or basename match, with an example). An agent can separate this from set_sprite_metadata, get_sprite_info, or open_sprite without opening the schema.

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?

Gives a clear usage context (live editor only, subsequent tools operate on the active sprite) and names the alternative route for the ambiguous case: unsaved sprites that share a name should be picked with pin_sprite. It stops short of covering other adjacent paths such as opening or creating a sprite first, so it is strong but not fully exhaustive.

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