Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

tilemap_fill_rect

Fill a rectangular area of a TileMap node with a specific tile in Godot, providing the start cell, width, height, and optional layer to populate multiple cells at once.

Instructions

Fill a rectangular area of a TileMap with a specific tile.

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>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "tilemap_fill_rect"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesTop-left cell X
yYesTop-left cell Y
layerNoTileMap layer index (default: 0)
widthYesFill width in cells
heightYesFill height in cells
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.9/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 behavioral burden. It does not disclose whether existing tiles in the rectangle are overwritten, whether an undo entry is created, whether the TileMap must already have the referenced TileSet source, or how errors (invalid node path, source ID) are surfaced.

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 zero filler, and the mutation target is stated immediately. Its brevity is efficient, though it shades into under-specification for a 7-parameter mutation tool.

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 7-parameter write operation with no annotations and no output schema, the description says nothing about return values, side effects, overwrite semantics, or failure modes. An agent would have to infer nearly all operational behavior from the schema alone.

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%, so all seven parameters, including layer defaulting to 0 and top-left/size semantics, are already documented in structured fields. The description adds no additional meaning, and its phrase 'specific tile' is not disambiguated against the bare source_id parameter, which lacks any atlas-coordinate counterpart.

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 (Fill), a specific resource (rectangular area of a TileMap), and the outcome (with a specific tile). An agent can distinguish this from tilemap_set_cell (single cell) and tilemap_clear without opening the schema, though it never says how the 'specific tile' is identified.

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?

The description provides no when-to-use guidance, no mention of alternatives such as tilemap_set_cell for single cells or tilemap_clear for erasing, and no prerequisites. The usage context is only inferred from the verb 'Fill' and the rectangle parameters.

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