Skip to main content
Glama
Sign In
Aseprite MCP

Aseprite MCP

by MalloyTheDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fill_tilemap

Fill an entire tilemap grid with a single tile index to set a uniform tile layer or clear existing tiles.

Instructions

Fill the entire tilemap grid with a single tile 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>",
      "tile_index": "<tile_index>"
    },
    "name": "fill_tilemap"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameNoDefault: 1.
layerYes
filenameYes
tile_indexYes

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 / tile_index / title
      Removed value: -"Tile Index"
    • removedInput schema / title
      Removed value: -"fill_tilemapArguments"
  2. First observedv0.7.0

TDQS

B3/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and openWorldHint=false, so the agent already knows this is a write operation. The description adds that it affects the entire tilemap grid, which usefully signals a bulk overwrite, but it does not disclose whether existing tiles are irreversibly replaced, what permissions are required, or how the optional frame parameter affects scope.

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?

The description is a single front-loaded sentence with no redundant or filler content. It efficiently communicates the core bulk-fill action without repeating schema details or annotations.

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 four-parameter mutation tool with low schema description coverage and no output schema, the description is too thin. It does not explain what filename or layer identify, how frame behaves, or what happens to existing tile data, so an agent lacks enough context to invoke it safely and correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%, and the description mentions only the concept of a single tile index, which maps weakly to the tile_index parameter. It provides no meaning for filename, layer, or frame, leaving three of four parameters semantically unexplained in both schema and description.

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 states a specific verb ('Fill') and resource ('entire tilemap grid') with the tile index constraint, so the core action is clear. However, it does not distinguish this operation from close siblings like fill_layer, fill_tile, set_tile, or set_tiles, leaving an agent to infer the difference from the name alone.

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 guidance on when to use this tool versus alternatives such as fill_layer, fill_tile, set_tile, or set_tiles. The description implies a bulk fill operation but does not state prerequisites, exclusions, or selection criteria for the agent.

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