Skip to main content
Glama
phaserjs

Phaser Editor MCP Server

Official
by phaserjs

scene-write-editable-tilemap-layer-data

Write tile data to a specific region of an editable tilemap layer, updating only the necessary tiles without resending the whole layer.

Instructions

Write part of the tile data of an editable tilemap layer. This is useful to update a layer's data without having to send the whole layer data again.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xYesThe x coordinate of the top left corner of the data to write.
yYesThe y coordinate of the top left corner of the data to write.
dataYesThe tile data to write to the layer. Each item is a tile ID, or -1 for an empty tile. The tile ID is a global ID that is computed by the index (starting from 1) of the tile in the tileset. If there are more than one tileset, then the global ID is computed by adding the length of each tileset. The data is a 2D array, where each inner array represents a row of tiles.
layerIdYesThe `id` of the editable tilemap layer to write to. An editable tilemap layer is also a game object, so you can use the `id` of the EditableLayer game object.
sceneIdYesThe `id` of the scene. The `id` is not the name of the scene, else a unique identifier is set in the scene data. You need to read the scene data to get the `id`.
Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose side effects, permissions, or constraints beyond the operation itself, such as whether data at coordinates is overwritten or if the layer must be editable.

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 concise at two sentences, front-loads the core purpose, and contains no unnecessary information.

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

Completeness4/5

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

Given the tool's simplicity, five parameters, and no output schema, the description adequately covers the use case. It could be more complete by mentioning coordinate system or error scenarios, but it is sufficient for agent selection.

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?

Schema description coverage is 100%, so baseline is 3. The description adds minimal value by restating what the schema already provides, though it clarifies the data format for tile IDs and empty tiles.

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 verb 'write', the resource 'part of the tile data of an editable tilemap layer', and distinguishes from the sibling tool 'scene-fill-editable-tilemap-layer-data' which writes the whole layer data.

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

Usage Guidelines4/5

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

The description explains when to use this tool ('update a layer's data without having to send the whole layer data again'), implying its utility for partial updates, but does not explicitly mention when not to use or name alternative tools.

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/phaserjs/editor-mcp-server'

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