Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

create_tilemap_layer

Creates a tilemap layer with its own tileset on a tile_width x tile_height grid, starting with only the reserved empty tile 0. Add editable tiles afterward with add_tile.

Instructions

Create a tilemap layer with its own tileset on a tile_width x tile_height grid. The new tileset starts with only tile 0, the reserved empty tile — use add_tile to append editable tiles. 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": {
      "name": "<name>",
      "tile_width": "<tile_width>",
      "tile_height": "<tile_height>"
    },
    "name": "create_tilemap_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
nameYes
tile_widthYes
tile_heightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/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 burden and does disclose real behavior: the new tileset is initialized with only the reserved empty tile 0, the operation is a single undo step, and headless calls require the file parameter. It omits what is returned and whether the new layer becomes the active/selected layer.

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?

Four short sentences, front-loaded with what is created, then initialization state, then undo, then the headless caveat. No padding; only minor friction from the literal double-backtick markup around ``file``.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 should say what the call yields, and it does not (return value, whether the layer is selected, what happens if a layer with that name exists). It is adequately complete on creation semantics and undo behavior but incomplete on results and error conditions.

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 4 parameters, so the description must compensate: it explains tile_width/tile_height as the grid dimensions and clarifies that file is only needed in headless mode. It adds nothing about name (naming rules, uniqueness, appearance in the layer list), leaving one of four parameters unexplained.

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?

States a specific verb and resource ("Create a tilemap layer") plus the scope ("with its own tileset on a tile_width x tile_height grid"), which is more precise than a bare restatement of the name. It does not explicitly contrast with sibling layer tools such as add_layer, so it falls short of full sibling differentiation.

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?

Gives useful follow-up routing ("use add_tile to append editable tiles") and a conditional instruction ("Headless: pass file"), but never says when to choose this over add_layer or create_slice, nor any prerequisites. Usage is implied rather than framed as when/when-not.

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