Skip to main content
Glama
phaserjs

Phaser Editor MCP Server

Official
by phaserjs

scene-add-editable-tilemap

Add an editable tilemap to a scene with custom dimensions and tilesets, enabling tile data modifications directly in the scene editor.

Instructions

Add an editable tilemap to the scene. An editable tilemap is different to a Tiled map because all the data can be edited by the user in the scene editor. However, it follows many of the concepts of Tiled. The editable tilemap is also a plain object so you can manipulate it using most of the plain object tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelYesLabel of the object. It is used to name the object in the scene and as the variable name in code.
widthYesThe width of the editable tilemap in tiles.
heightYesThe height of the editable tilemap in tiles.
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`.
tilesetsYesThe tilesets used by the tilemap.
tileWidthYesThe width of each tile in pixels.
tileHeightYesThe height of each tile in pixels.
Behavior2/5

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

No annotations provided, so description must carry full burden. Discloses that the tilemap is editable and a plain object, but omits side effects, error conditions, or required permissions.

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?

Three sentences, front-loaded with action, no redundancy. Could be more concise 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?

With 7 required parameters and no output schema, description lacks return type information and does not fully contextualize the tool's role among siblings. Missing detail on what the tool produces.

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 coverage is 100% with descriptions for each parameter. Description adds no additional meaning beyond 'follows Tiled concepts', so baseline of 3 is appropriate.

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?

Clearly states it adds an editable tilemap, contrasting with Tiled maps. However, does not explicitly differentiate from sibling tools like scene-add-editable-tilemap-layer.

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?

Implies usage for creating an editable tilemap, but no explicit when-to-use or alternatives provided. Lacks prerequisites or exclusion criteria.

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