Skip to main content
Glama
Sign In
Aseprite MCP

Aseprite MCP

by MalloyTheDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_tile

Places a tile from a tileset at a specified grid cell (column, row); use tile index 0 for empty.

Instructions

Place a tile (by tileset index, 0 = empty) at grid cell (column, row).

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>",
      "column": "<column>",
      "row": "<row>",
      "tile_index": "<tile_index>"
    },
    "name": "set_tile"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowYes
frameNoDefault: 1.
layerYes
columnYes
filenameYes
tile_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.10.0
    • removedInput schema / properties / column / title
      Removed value: -"Column"
    • 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 / row / title
      Removed value: -"Row"
    • removedInput schema / properties / tile_index / title
      Removed value: -"Tile Index"
    • removedInput schema / title
      Removed value: -"set_tileArguments"
  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 already declare readOnlyHint=false and openWorldHint=false, so the agent knows this mutates local state. The description adds only the "0 = empty" clearing behavior; it says nothing about whether the tileset/file must already exist, whether the change persists, or error behavior.

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?

A single tight sentence with the key index semantics parenthesized inline; nothing is wasted and the operation is front-loaded. It is efficient, though very sparse for a 5-required-parameter mutation.

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?

For a 6-parameter mutation tool with no output schema and 17% schema coverage, the definition is too thin: filename/layer semantics, save behavior, and failure modes are all unaddressed, so an agent cannot reliably call it without guessing.

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 only 17%, so the description carries heavy burden. It usefully explains tile_index (tileset index, 0 = empty) and maps column/row to a grid cell, but leaves the required filename, layer, and the optional frame parameter completely 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+resource ("Place a tile") and a precise target ("grid cell (column, row)"), and clarifies tile_index semantics ("0 = empty"). However, it does not distinguish itself from the cluster of highly similar siblings (add_tile, set_tiles, fill_tile, paint_tile_pixels), leaving the agent to infer the difference.

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 prerequisites, and no mention of the near-identical tile siblings. With add_tile, set_tiles, fill_tile and fill_tilemap all in scope, the absence of any routing guidance is a clear gap.

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