Skip to main content
Glama

create_tilemap_layer

Create an empty tilemap layer for grid-based sprite editing. Define tile dimensions and grid size to structure your canvas for tile-based assets.

Instructions

Create a tilemap layer with an empty grid.

Args:
    name: Layer name.
    tile_width, tile_height: Tile size in pixels (sets the sprite grid).
    columns, rows: Grid size in tiles (default: enough to cover the canvas).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
rowsNo
frameNo
columnsNo
filenameYes
tile_widthNo
tile_heightNo
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions creation (mutation) but lacks details on side effects, required permissions, or any constraints (e.g., whether the sprite must exist). The empty grid implication is noted, but overall transparency is low.

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 brief (one sentence plus an Args list) and front-loaded. Every sentence adds value, though the list format is clear. Could be slightly improved by reordering or formatting, but overall efficient.

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?

Given the lack of output schema and the presence of a required but unexplained parameter (filename), the description is incomplete. It does not explain what the tool returns or how the filename relates to the layer creation, leaving agents potentially confused.

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?

The schema has 0% description coverage, so the description must compensate. It explains tile_width, tile_height, columns, and rows with meaningful context (sets grid, covers canvas). However, it omits the required 'filename' and optional 'frame', leaving those parameters ambiguous. Partial but incomplete compensation.

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 clearly states the action ('Create a tilemap layer') and the object ('with an empty grid'), which distinguishes it from sibling tools like add_layer or add_group_layer. However, it fails to mention the required 'filename' parameter, which is crucial for understanding what sprite context the layer is created in.

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 add_layer or add_group_layer. The context signals show numerous sibling tools, but the description does not help an agent choose this tool over others.

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