Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

open_sprite

Opens a sprite file as the active Aseprite document and returns its filename, size, frame and layer counts; in headless mode, verify Aseprite can read it before editing.

Instructions

Open a sprite file and make it the active document; returns its filename, size, and frame/layer counts. Live: opens a new tab in the editor and makes it the sprite Claude works on. Headless: each call is a fresh process, so this is a "can Aseprite read this file" probe returning the file's info — to edit a file headless, pass it as the file argument of the editing tools instead.

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": {
      "path": "<path>"
    },
    "name": "open_sprite"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations beyond a title, the description carries the full behavioral burden and does it well: it discloses the side effect (new tab, becomes the active document), the statefulness model (headless calls are fresh processes, so nothing persists), and the resulting read-only probe semantics. It stops short of saying what happens if the path is already open, or which formats are accepted.

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 core action and return values, then the mode split. The inline 'Live:'/'Headless:' markers aid scanning, though the line-broken formatting and the nested quote in the headless clause add slight noise.

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?

No output schema exists, so the description correctly compensates by listing what is returned (filename, size, frame/layer counts). For a one-parameter tool with no annotations, the only real omission is the path contract and duplicate-open behavior.

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% for the single ``path`` parameter, and the description never clarifies whether the path must be absolute, whether an extension is required, or what happens on an unreadable/unsupported file. The usage sentence implies the path points at an on-disk sprite file, which is some added meaning, but it leaves the actual path contract unspecified.

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 ('Open a sprite file and make it the active document') plus the return payload (filename, size, frame/layer counts), which separates it from create_sprite and set_active_sprite. The live-vs-headless framing further sharpens what the call actually does in each mode.

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

Usage Guidelines5/5

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

Explicitly tells the agent when this is the right call (live: open a tab and make it the active document) and when it is not (headless: use the ``file`` argument of the editing tools instead of opening). It names the alternative mechanism rather than leaving the agent to guess.

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