Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

add_tile

Append an empty tile to a tilemap layer's tileset and return the new tile index plus updated tileset size, enabling incremental tilemap expansion in Aseprite projects.

Instructions

Append an empty tile to a tilemap layer's tileset; returns the new tile's index and the tileset size. The first added tile is index 1 (tile 0 is the reserved empty tile). One undo step. Headless: pass file.

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": {
      "layer": "<layer>"
    },
    "name": "add_tile"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
layerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations carry only a title, so the description bears the disclosure burden and does well: it states the return values (new tile index and tileset size), the indexing convention (first added tile is index 1, tile 0 reserved), that the operation is a single undo step, and the headless/file requirement. It does not mention permissions or failure modes, which keeps it just short of the top.

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 clauses, each front-loaded with a distinct fact: action, return values, indexing caveat, undo behavior, headless requirement. No filler and nothing repeated from the schema.

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 two-parameter tool with no output schema, the description supplies the return semantics and the indexing convention that an agent would otherwise get wrong. Only the parameter formats remain unclear, which is a modest gap.

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 clarifies that ``file`` is needed in headless mode, but neither parameter's expected format (e.g., whether ``layer`` is a name or index, what path ``file`` expects) is explained, so meaning is only partially filled in.

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 uses a specific verb ('Append') and a precise resource ('an empty tile to a tilemap layer's tileset'), so the agent knows exactly what the call creates. It doesn't explicitly contrast with siblings like add_layer or draw_on_tile, but the object being appended is unambiguous enough to distinguish it.

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?

There is no explicit when-to-use or when-not-to-use guidance relative to alternatives. The only conditional instruction is 'Headless: pass ``file``', which tells the agent when that parameter is required but leaves the broader selection context implied.

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