Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

tilemap_get_used_cells

Retrieve all used cell coordinates from a specified TileMap layer to inspect occupied tiles and support tile-based processing in Godot.

Instructions

Get all used cell coordinates 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_get_used_cells"
  }
}

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

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of disclosure. 'Get' implies a read-only operation, but nothing is said about the return shape (flat list vs. coordinate pairs), ordering, behavior for an empty layer or an invalid layer index, or cost on large maps.

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?

A single front-loaded sentence with no filler. It is efficient, though so terse that it leaves observable gaps instead of using the space it saves.

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

Completeness3/5

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

For a two-parameter read tool without annotations or an output schema, the definition is minimally adequate. The main missing piece is what the returned coordinates look like, which the description must cover since no output schema exists.

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 both node_path and layer are already documented in the schema, including the default of 0. The description adds no meaning beyond that and does not explain layer semantics such as what happens for an out-of-range index.

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?

The description names a specific verb and resource: get all used cell coordinates in a TileMap layer. That is enough to separate it from siblings like tilemap_set_cell or tilemap_clear, but it never explicitly contrasts with tilemap_get_info, which an agent might reasonably confuse it with.

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?

Usage is only implied: the phrase 'used cell coordinates' hints that you call this when you need to enumerate occupied cells. No explicit when-to-use, prerequisites, or named alternatives (e.g. tilemap_get_info for metadata) are given.

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