Skip to main content
Glama

tilemap

Create and manage Unity Tilemaps for 2D level design. Place, erase, fill, and inspect tiles, compress bounds, and control tile colors.

Instructions

Manage Unity Tilemaps for 2D level design. Actions:

  • create: Create a new Tilemap under a Grid (creates Grid if needed)

  • get_info: Get tilemap details (bounds, tile count, orientation)

  • set_tile: Place a tile at a cell position

  • erase_tile: Remove a tile at a cell position

  • fill_area: Fill a rectangular area with a tile

  • clear: Remove all tiles from a tilemap

  • get_tile: Inspect what tile is at a cell position

  • get_bounds: Get the used cell bounds

  • list: List all tilemaps in the scene

  • list_tiles: List TileBase assets in a folder

  • create_tile: Create a Tile asset from a sprite

  • set_color: Set the color tint of a tile at a position

  • compress_bounds: Compress tilemap bounds to remove empty space

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aNoAlpha color component (0-1)
bNoBlue color component (0-1)
gNoGreen color component (0-1)
rNoRed color component (0-1)
xNoCell X position
yNoCell Y position
endXNoFill area end X
endYNoFill area end Y
nameNoName for new tilemap (create)
colorNoColor JSON for create_tile: {"r":1,"g":1,"b":1,"a":1}
actionYesTilemap action to perform
folderNoFolder to search for tiles (default: Assets)
startXNoFill area start X
startYNoFill area start Y
tilePathNoAsset path to a TileBase or Tile
tilemapIdNoInstance ID of the Tilemap
parentPathNoParent Grid path (create)
spritePathNoSprite path for create_tile
tilemapNameNoName of the Tilemap GameObject
sortingOrderNoSorting order (create)
Behavior4/5

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

Annotations indicate readOnlyHint=false, and the description lists both read and write actions, disclosing mutability. No contradictions with annotations. However, it does not explicitly state which actions are destructive or their side effects beyond the brief action descriptions.

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 opens with a clear one-line purpose, followed by a structured list of actions. While the list is somewhat lengthy, it is well-organized and front-loaded. Each action description is concise.

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

Completeness3/5

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

Given the tool's complexity (20 parameters, 13 actions) and lack of output schema, the description provides only high-level action summaries. It does not specify parameter requirements per action or return values, leaving gaps for correct invocation.

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 input schema has 100% description coverage, so the baseline is 3. The description adds context by grouping parameters under actions, but does not explain parameter relationships or provide additional meaning beyond the schema definitions.

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 'Manage Unity Tilemaps for 2D level design' and enumerates 13 specific actions, making the tool's purpose unambiguous. It distinguishes itself from sibling tools, none of which target tilemaps.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use for tilemap operations but provides no explicit guidance on when to use this tool versus alternatives, nor any exclusion criteria. The sibling list is diverse, so the tool is clearly specialized, but no usage context is given.

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/joel-wehr/unity-mcp'

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