Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

tilemap_clear

Clears all cells in a specified TileMap layer to reset the tilemap for new level layouts or edits.

Instructions

Clear all cells in a TileMap layer.

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>"
    },
    "name": "tilemap_clear"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerNoTileMap layer index (default: 0)
node_pathYesPath to the TileMap node

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 the full behavioral burden. It says 'clear all cells' but never discloses that this is a destructive, likely irreversible mutation, whether it is undoable, whether only the specified layer is affected while other layers are preserved, or what happens if the layer index is out of range.

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?

One front-loaded sentence with no filler, and the scope-restricting word 'all' appears early. It is efficient, though efficient to the point of under-specifying a destructive operation.

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 destructive mutation with no annotations and no output schema, the definition should state irreversibility, layer scoping, and whether a count of cleared cells is returned. None of that is present, so an agent could invoke it without understanding the consequences.

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%, with both node_path and layer already documented including the default of 0. The description adds only the notion that clearing is scoped to the layer, which the schema implies; 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 and resource: clearing all cells in a TileMap layer, targeting the node at node_path. An agent can distinguish this from tilemap_set_cell and tilemap_fill_rect, but the description never names those siblings or draws the line explicitly.

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 guidance on when to use this versus tilemap_fill_rect or tilemap_set_cell, no prerequisite conditions, and no caveat about needing confirmation before wiping a layer. The agent must infer the use case entirely from the name.

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