Skip to main content
Glama

add_gridmap

Create a GridMap node for 3D tile-based level design, specifying parent path and optional properties like mesh library path and cell size.

Instructions

Add a GridMap node for 3D tile-based level design

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parentYesParent node path. Use '' (empty string) to add at scene root, or a node name/path (e.g. 'Player' or 'Player/Sprites') to add as a child of that node.
propertiesNoGridMap properties (mesh_library_path, cell_size, etc.)
Behavior2/5

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

No annotations provided; description only states that a GridMap node is added, with no mention of side effects, editor state changes, or required permissions. Insufficient for a mutation tool.

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?

Single sentence with no wasted words, clearly communicating the tool's primary purpose. Efficient and front-loaded.

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?

Lacks details about the properties parameter, return values, and typical use cases. For a tool with nested objects and no output schema, more context is needed to ensure correct invocation.

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%; the description adds no extra meaning beyond the schema. Baseline score of 3 is appropriate as it does not detract but also adds no value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Add' and resource 'GridMap node' with specific context 'for 3D tile-based level design', distinguishing it from generic siblings like add_node or add_scene_instance.

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 guidance on when to use this tool versus alternatives such as add_node or other add_* tools. Missing prerequisites, context, or exclusions.

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/KeeVeeG/godot-mcp'

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