Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

tilemap_get_info

Retrieves TileMap node details such as layers, cell size, and used rect so you can inspect or debug Godot tile layouts.

Instructions

Get information about a TileMap node (layers, cell size, used rect, etc.).

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_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesPath to the TileMap node

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It makes clear this is a non-mutating inspection call and lists what kinds of data come back. It does not say whether the node must exist in the edited scene, what happens if the path is not a TileMap, or whether an open editor/running game is required.

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. The trailing "etc." slightly weakens precision by leaving the return contents open-ended, but the core is stated immediately.

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?

A simple one-parameter read tool, but with no output schema the description is the only source of return-value information, and "etc." leaves that incomplete. It is adequate to call the tool correctly but not to predict the response shape.

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% for the single node_path parameter, so the schema already explains it. The description adds nothing about path format or resolution rules beyond the schema's "Path to the TileMap node". Baseline 3 applies when the schema does the work.

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 ("Get information about a TileMap node") and enumerates the payload categories: layers, cell size, used rect. That is far more informative than a tautology. It stops short of naming how it differs from close siblings such as tilemap_get_used_cells, which returns a subset of the same data.

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 statement of when to use this versus tilemap_get_used_cells or the mutation tools like tilemap_set_cell/tilemap_clear. Usage is only implied by the word "Get". An agent must infer that this is the broad read-first inspection tool.

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