Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

create_sprite

Creates a new Aseprite sprite at a set width, height, and color mode, either as a live untitled canvas Claude controls or as a saved .aseprite file for headless work.

Instructions

Create a new sprite. Live: opens a new untitled sprite in the editor and makes it the sprite Claude works on, even if the artist clicks another tab. Headless: writes a new .aseprite to file (required). color_mode is one of rgb | gray | indexed.

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": {
      "width": "<width>",
      "height": "<height>"
    },
    "name": "create_sprite"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
widthYes
heightYes
color_modeNorgb

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the write/safety profile is covered. The description usefully adds that live mode makes the new sprite the active one 'even if the artist clicks another tab' (a real side effect) and that headless writes a file to disk. It omits whether an existing file at `file` is overwritten and what the call returns, which matters for a non-idempotent write.

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?

Three tight sentences, front-loaded with the core action, then mode-specific behavior, then the enum constraint. No filler or restatement of the name.

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 4-parameter creation tool with no output schema, the description covers the mode split, the file requirement, and color modes adequately. The remaining gap is the return value (e.g., a sprite handle needed by later calls) and overwrite semantics for the headless path.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden, and it does real work: it explains the conditional requirement on `file` and enumerates `color_mode` values (rgb | gray | indexed) that the schema leaves as a bare string with no enum. Width and height are left undocumented, though their meaning is self-evident.

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?

The description opens with a specific verb+resource ('Create a new sprite') and immediately splits the behavior into the two execution contexts (Live vs Headless). That framing makes it unmistakable against siblings like open_sprite, set_active_sprite, or add_frame.

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 conditional usage guidance: in headless mode a `file` path is required, while live mode operates on the editor. It does not explicitly say when to prefer this over open_sprite for an existing file, but the create-vs-open split is implicit and clear.

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