Skip to main content
Glama
Sign In
Godot MCP - Full Control

Godot MCP - Full Control

by cxb2523
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_tilemap

Get, set, or erase cells in a TileMapLayer node to edit game tilemaps, and retrieve used cells for efficient level design.

Instructions

Get or set cells in a TileMapLayer node

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "nodePath": "<nodePath>",
      "action": "<action>"
    },
    "name": "game_tilemap"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoCell X coordinate (for get_cell)
yNoCell Y coordinate (for get_cell)
cellsNoArray of cell objects for set_cells/erase_cells
actionYesAction: set_cells, get_cell, erase_cells, get_used_cells
nodePathYesPath to TileMapLayer node
sourceIdNoFilter by source_id (for get_used_cells)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries full behavioral burden, yet it says nothing about the fact that set_cells and erase_cells mutate the tilemap while the other actions read, nor whether the target node must be in the running scene versus an edited scene, nor anything about undo, errors, or permissions. For a mixed read/write tool this is a substantial gap.

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?

A single nine-word sentence with zero waste, but it is front-loaded with almost nothing useful for a six-parameter, four-action tool. Brevity here reads as under-specification rather than discipline.

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 no annotations, no output schema, and four distinct actions, the description should at least indicate what get_cell and get_used_cells return and that the set/erase actions change state. None of that is present, so the definition is not complete enough for the tool's complexity.

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% and every parameter, including the action list (set_cells, get_cell, erase_cells, get_used_cells), is documented in the schema itself. The description adds no meaning beyond that, so the baseline 3 applies.

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?

States a specific verb pair and resource: "Get or set cells in a TileMapLayer node." An agent can tell this is the tilemap-cell accessor, but nothing distinguishes it from sibling tools like game_gridmap, game_terrain, or game_get_property.

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 on when to use this versus game_gridmap or game_terrain, and no guidance on choosing among the four actions. The only selection hints live in the schema's per-parameter descriptions, not the tool description.

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

Deploy Server

Other Tools