Skip to main content
Glama

tilemap

Destructive

Read, copy, edit, fill, clear, paste, and transform TileMap nodes in Godot at runtime, with operations affecting only the current execution context.

Instructions

TileMap/TileMapLayer 图块操作。读取: tilemap_read, tilemap_copy。写入: tilemap_set_cell, tilemap_erase_cell, tilemap_fill_rect, tilemap_clear, tilemap_paste, tilemap_set_transform。运行时操作,仅影响当前执行上下文。如需持久化,请编辑 .tscn 文件。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
layerNo图层索引(可选,默认 0)。tilemap_read/set_cell/erase_cell/fill_rect/copy/paste/set_transform 使用;tilemap_clear 不传则清除所有图层
actionYes操作类型
coordsNo图块坐标 Vector2i。tilemap_set_cell/erase_cell/set_transform 使用
flip_hNo水平翻转(可选,默认 false)。tilemap_set_transform 使用
flip_vNo垂直翻转(可选,默认 false)。tilemap_set_transform 使用
regionNo矩形区域 Rect2i。tilemap_read: 读取区域(可选,不传则读取全部已用图块);tilemap_fill_rect: 填充区域
targetNo粘贴目标坐标 Vector2i。tilemap_paste 使用
patternNo图块图案(由 tilemap_copy 返回的 pattern 对象)。tilemap_paste 使用
node_pathNoTileMap/TileMapLayer 节点路径(如 root/Level/TileMap)
source_idNoTileSet 源 ID。tilemap_set_cell/fill_rect 使用
transposeNo转置(可选,默认 false)。tilemap_set_transform 使用
atlas_coordsNo图集坐标 Vector2i。tilemap_set_cell/fill_rect 使用
project_pathNoGodot 项目目录路径(可选,默认使用 GODOT_PROJECT_PATH 环境变量或当前目录)
source_regionNo源区域 Rect2i。tilemap_copy 使用
load_autoloadsNo是否加载 Autoload 上下文(默认 true)
alternative_tileNo替代图块索引(可选,默认 0)。tilemap_set_cell/fill_rect 使用
Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds valuable context that changes are runtime-only and not persisted, which clarifies the blast radius. It also lists all actions, implicitly showing which are destructive. This goes beyond the annotations and helps set expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with clear structure: it names the resource, lists read and write actions, and states the key behavioral constraint. Every sentence earns its place, and there is no redundancy or fluff.

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?

The tool is complex (16 parameters, 8 actions, nested objects) with no output schema. The description covers the overall context and persistence behavior, but it does not explain what each action returns or provide examples. The schema documents parameters well, so the overall package is adequate but has gaps in action-level semantics and return values.

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 16 parameters are already documented with per-action usage hints. The description itself adds little beyond grouping actions into read/write categories, which is useful but does not enhance parameter semantics. Baseline 3 applies because the schema carries the full burden.

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 clearly identifies the resource (TileMap/TileMapLayer) and enumerates the specific read/write operations it supports. It distinguishes the tool from generic scene/editor tools by focusing on tile-level manipulations. However, it does not state a single primary action, so it is not as crisp as a tool with a single verb+resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage context: it is a runtime operation affecting only the current execution context, and persistence requires editing the .tscn file. It also categorizes actions as read vs. write, which helps the agent choose the right action. It does not name alternatives among sibling tools, but the guidance is otherwise clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wgt19861219/godot-mcp-enhanced'

If you have feedback or need assistance with the MCP directory API, please join our Discord server