tilemap_clear
Clears tile cells from a TileMap node, either in a specified area or across the entire map.
Instructions
Clear cells in a TileMap area or the entire map
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | TileMap node path |
Clears tile cells from a TileMap node, either in a specified area or across the entire map.
Clear cells in a TileMap area or the entire map
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | TileMap node path |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavior. It only states 'clear cells' without mentioning whether the operation is destructive, affects all layers, is undoable, or requires specific permissions. For a mutation tool, this is a significant gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single short sentence, which is efficient. However, it could be slightly more informative without being verbose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity of the tool (one parameter, no output schema), the description is missing critical behavioral information. The mismatch between 'area or entire map' and the schema's single path parameter also reduces completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with one parameter 'path'. The description does not add much beyond the schema: it says 'area or the entire map' but doesn't explain how the path relates to area specification. Baseline 3 is appropriate as schema already documents the parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool clears cells in a TileMap, using a specific verb and resource. It distinguishes from siblings like tilemap_set_cell and tilemap_fill_rect by focusing on clearing. However, the mention of 'area or the entire map' is not reflected in the schema (only a path parameter), which slightly reduces clarity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use (when you want to clear cells) but does not explicitly state alternatives or when not to use. Given sibling tools like tilemap_fill_rect and tilemap_set_cell, more explicit guidance would be beneficial.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/KeeVeeG/godot-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server