Skip to main content
Glama
aseprite-claude-connector

aseprite-claude-connector

make_autotiles

Builds a 47-tile autotile set for a fill terrain over a base layer or clear, so map painters select correct edges and corners, and exports PNG plus Godot TileSet or Unity Rule Tile assets.

Instructions

Build the 47-tile autotile set for one terrain (fill_layer, like grass) over another (base_layer, like dirt, or clear), so a map painter picks the right edge and corner for every neighbour. Both textures come from the top-left size square of their layer, so make_seamless them first. edge is how far the fill stops from an open side, and outline gives its border a darker shade of its own colours. Writes name.png. With game_dir (or the remembered game folder, if out_dir isn't given), a Godot project also gets name.tres, a TileSet whose terrain paints the set, and a Unity project gets the sheet sliced into tiles plus name_rule.asset, a Rule Tile (needs the 2D Tilemap Extras package). out_dir writes the PNG and a JSON map of each tile's neighbours. Returns a picture of the set. 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": {
      "fill_layer": "<fill_layer>",
      "size": "<size>",
      "name": "<name>"
    },
    "name": "make_autotiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgeNo
fileNo
nameYes
sizeYes
frameNo
out_dirNo
outlineNo
game_dirNo
base_layerNo
fill_layerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only supply destructiveHint=false, so the description carries most of the weight and does so well: it discloses that files are written (name.png, name.tres, name_rule.asset, JSON map), that the Unity path depends on the 2D Tilemap Extras package, and that the call returns a picture of the set. These are material side effects and dependencies an agent could not learn from the annotations alone.

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 text is front-loaded with the core purpose before branching into platform-specific outputs, and every sentence conveys a distinct fact about inputs, side effects, or return value. It is dense and slightly long, but the length is justified by the tool's complexity rather than padding.

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?

With no output schema, the description covers the return value ('Returns a picture of the set') and all output artifacts, plus the headless escape hatch. Completeness is only slightly undercut by the undocumented 'frame' parameter and the lack of detail on how the JSON neighbour map is keyed.

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 coverage is 0% across 10 parameters, so the description must supply the meaning, and it does for most: fill_layer/base_layer roles, size as the top-left square to sample, edge as the distance the fill stops from an open side, outline as a darker self-shade, and the game_dir/out_dir/file channels. The 'frame' parameter (default 1) is never mentioned, leaving one gap in an otherwise thorough mapping.

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 states a specific verb and resource ('Build the 47-tile autotile set for one terrain over another') and immediately names the two roles, fill_layer and base_layer, with concrete examples (grass over dirt). An agent can tell this apart from sibling texture tools such as make_seamless without reading the schema.

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?

It gives explicit prerequisites ('make_seamless them first') and routes between output modes: game_dir for a Godot TileSet or Unity Rule Tile, out_dir for a PNG plus JSON neighbour map, and file for headless use. The conditional 'the remembered game folder, if out_dir isn't given' clarifies precedence between alternatives rather than leaving it to inference.

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