Skip to main content
Glama
Sign In
Aseprite MCP

Aseprite MCP

by MalloyTheDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fill_tile

Fill an existing Aseprite tile's artwork with a solid color. Specify filename, layer, tile index, and color to repaint that tile area.

Instructions

Fill an existing tile's artwork with a solid colour.

Returns `pixels` (the tile's area, all of which is written) so the result says the fill
reached the tile rather than only that the call returned.

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>",
      "color": "<color>"
    },
    "name": "fill_tile"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorYes
frameNoDefault: 1.
layerYes
filenameYes
tile_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.10.0
    • removedInput schema / properties / color / title
      Removed value: -"Color"
    • 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_tileArguments"
  2. First observedv0.7.0

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare this is not a read-only operation and is not open-world. The description adds meaningful context by stating that all of the tile's area is written and that the return value reports the filled pixels rather than merely call success.

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 description is short and front-loads the purpose in the first sentence. The second sentence explains the return value and is useful, though slightly more verbose than strictly necessary.

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?

No output schema exists, and the description does provide some return-value context. However, for a five-parameter mutation tool with only 20% schema description coverage, it leaves most parameter semantics unexplained and is not complete enough for reliable invocation.

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 20%, with just the frame parameter documented. The description implies color is a solid colour and that tile_index identifies the existing tile, but it does not explain filename, layer, tile_index, or frame semantics.

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 and resource: 'Fill an existing tile's artwork with a solid colour.' This distinguishes it from layer-level or tilemap-level fills, though it does not explicitly name the sibling tools it differs from.

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?

The description gives no when-to-use guidance, no prerequisites, and no comparison to alternatives such as fill_layer, fill_tilemap, or paint_tile_pixels. It only implies that the tile must already exist.

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