tilemap_get_info
Retrieve configuration and TileSet details of a TileMap node by specifying its path.
Instructions
Get TileMap configuration and TileSet information
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | TileMap node path |
Retrieve configuration and TileSet details of a TileMap node by specifying its path.
Get TileMap configuration and TileSet information
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | TileMap node path |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description does not disclose side effects or safety (though read-only is implied). Minimal but adequate for a simple info tool.
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?
Single concise sentence with no filler, directly conveying purpose.
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?
Description covers purpose well, but omits details on return format or structure. Given simplicity and no output schema, it is slightly incomplete but still usable.
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?
Only parameter 'path' is fully described in schema (100% coverage). Description adds no additional semantic detail beyond schema.
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?
Description clearly states verb 'Get' and resource 'TileMap configuration and TileSet information', distinguishing it from sibling tools that modify tilemaps (e.g., tilemap_set_cell, tilemap_clear).
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?
No explicit guidance on when to use this tool versus alternatives like tilemap_get_cell. Siblings imply this is for overall info, but lack of explicit direction is a gap.
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