Skip to main content
Glama
Sign In
Aseprite MCP

Aseprite MCP

by MalloyTheDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_tiles

Place multiple tiles at once in a sprite layer by specifying each tile's column, row, and index, so AI agents can build tilemaps without repeated single-tile calls.

Instructions

Place many tiles at once. tiles: list of {"column", "row", "index"}.

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": {
      "filename": "<filename>",
      "layer": "<layer>",
      "tiles": "<tiles>"
    },
    "name": "set_tiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameNoDefault: 1.
layerYes
tilesYes
filenameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.10.0
    • removedInput schema / properties / filename / title
      Removed value: -"Filename"
    • addedInput schema / properties / frame / description
      Added value: +"Default: 1."
    • removedInput schema / properties / frame / title
      Removed value: -"Frame"
    • removedInput schema / properties / layer / title
      Removed value: -"Layer"
    • removedInput schema / properties / tiles / title
      Removed value: -"Tiles"
    • removedInput schema / title
      Removed value: -"set_tilesArguments"
  2. First observedv0.7.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and openWorldHint=false, so the write nature is already covered. The description adds nothing beyond that: it doesn't say whether existing tiles are overwritten, whether 'index' refers to a tileset index or -1 for empty, or whether filename/layer must pre-exist.

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 short sentences, front-loaded with the action and followed by the payload shape, with no filler. It is lean almost to the point of being terse, but nothing is wasted.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A mutation tool on a tilemap layer with four parameters, 25% schema coverage, no output schema, and dense tile siblings — the description should do much more. It omits what the operation mutates, overwrite behavior, and how it differs from the other tile tools.

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 coverage is only 25% (only 'frame' is documented), so the description must compensate. It partially does by disclosing the tile object shape {column, row, index}, which is genuinely useful since the schema types 'tiles' items as an opaque object. But filename, layer, and frame semantics remain 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 ('Place many tiles at once'), and the plural quantity implicitly distinguishes it from the singular set_tile. However, it never names or contrasts with the nearby siblings set_tile, add_tile, fill_tile, or fill_tilemap, leaving the agent to infer which tile-writing tool applies.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no alternatives named, despite four tile-manipulation siblings (set_tile, add_tile, fill_tile, fill_tilemap) whose boundaries an agent needs resolved. The agent gets no signal about batch-vs-single or paint-vs-place selection.

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