Skip to main content
Glama

fill_tile

Fill a tile in an Aseprite sprite with a solid colour, specifying the tile index, layer, frame, and colour.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorYes
frameNo
layerYes
filenameYes
tile_indexYes
Behavior2/5

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

No annotations exist, and the description does not disclose whether the fill overwrites existing artwork, requires the tile to exist, or how it interacts with layers or frames. Minimal behavioral context is provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no waste, but it lacks structural elements like when-to-use or parameter hints. While concise, it is under-informative for a tool with five parameters.

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

Completeness1/5

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

Given the tool has 5 parameters, no output schema, and no annotations, the description is far too minimal. It does not explain the filling process, required preconditions, or return behavior, leaving the agent with insufficient context.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain any parameter (e.g., color format, layer meaning, tile_index requirement). The agent has no guidance on parameter semantics beyond the schema's property names.

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 clearly states the action ('fill'), target ('existing tile's artwork'), and medium ('solid colour'). It distinguishes from siblings like fill_area or fill_layer by specifying 'tile', which is unique among the many fill tools.

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?

No guidance is provided on when to use this tool versus alternatives such as fill_area, fill_layer, or paint_tile_pixels. The agent must infer from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MalloyTheDev/aseprite-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server