Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

tilemap_set_cell

Sets a single cell on a Godot TileMap node using X/Y coordinates and optional layer, source, and atlas tile coordinates.

Instructions

Set a single cell in a TileMap 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": {
      "node_path": "<node_path>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "tilemap_set_cell"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesCell X coordinate
yYesCell Y coordinate
layerNoTileMap layer index (default: 0)
atlas_xNoAtlas tile X coordinate
atlas_yNoAtlas tile Y coordinate
node_pathYesPath to the TileMap node
source_idNoTileSet source ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the entire behavioral burden. It does not say whether the operation mutates scene state persistently, what happens when source_id or atlas coordinates are omitted (erase vs. no-op), or what the call returns or raises on an invalid node_path.

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 short sentence with no filler, but its brevity comes at the cost of under-specification rather than disciplined economy. It is front-loaded with the verb and resource, which helps.

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?

For a seven-parameter mutating tool with no annotations and no output schema, the description is far too thin. It should at minimum explain the interaction between source_id/atlas coordinates and the resulting cell state, which is the main ambiguity an agent faces.

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 all seven parameters, including layer default, atlas coordinates, and source_id, are already documented in the schema. The description adds no meaning beyond that, so the baseline of 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?

A specific verb plus resource: "Set a single cell in a TileMap node." The word "single" implicitly separates it from bulk siblings like tilemap_fill_rect and tilemap_clear, though no sibling is named and no routing statement is made.

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?

There is no explicit when-to-use guidance, no mention of when to prefer tilemap_fill_rect or tilemap_clear, and no preconditions such as the node existing or a TileSet being assigned. The only cue is the word "single".

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