Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

pin_sprite

Idempotent

Locks editing tools to a chosen Aseprite sprite by filename, tag, or the artist's current tab, so edits stay on target while other files are viewed.

Instructions

Live editor only: choose the sprite Claude's edits go to. Every tool then works on it even while the artist looks at another tab. Pick it by filename (full path or basename), by a tag it has (the way to tell unsaved sprites apart), or give neither to pin the sprite the artist has open now ("work on this one"). unpin goes back to following whichever sprite is active. Sprites Claude creates or opens are pinned on their own.

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

Input Schema

NameRequiredDescriptionDefault
tagNo
unpinNo
filenameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior4/5

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

Only idempotentHint is supplied, so the description carries most of the burden and does so well: it discloses that the pin persists across every subsequent tool call, that it overrides the artist's visible tab, that created/opened sprites auto-pin, and that unpin restores follow-the-active-sprite behavior. It omits what happens on a failed or ambiguous filename/tag match, which matters for a stateful switch.

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?

The most important constraint ('Live editor only') is front-loaded, and the three selection modes are enumerated compactly with parentheticals that clarify rather than pad. Slightly dense but no sentence is wasted.

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 stateful, no-output, minimally annotated tool with three undocumented parameters, the description covers the mechanics, side effects, and reversal path an agent needs. Only error/ambiguity handling and the relationship to set_active_sprite are left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 define all three parameters, and it does: filename accepts a full path or basename, tag exists specifically to address unsaved sprites, unpin reverts to active-sprite following, and passing neither pins the currently open sprite. This adds genuine meaning the bare schema does not convey.

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 opens with a specific verb and resource ('choose the sprite Claude's edits go to') and scopes it ('Live editor only'), so the agent immediately knows this sets an edit target rather than performing an edit. It does not explicitly distinguish itself from the similarly named set_active_sprite sibling, which is the one place clarity could be sharper.

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?

It gives concrete selection conditions: by filename (full path or basename), by tag for unsaved sprites, or neither to grab the artist's currently open sprite, plus the unpin escape hatch. The 'live editor only' preface acts as a when-not signal. It never names an alternative tool for the non-live case, so it falls short of full when/when-not 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