Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_gridmap

Create GridMap nodes in Godot scenes to enable AI-driven 3D grid-based level design and automated tile placement.

Instructions

Create GridMap node. (Compatibility tool)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "add_gridmap"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. While 'Create' implies a write operation, the description fails to explain what 'compatibility tool' means (deprecated API? legacy mode?), what side effects occur, or why the parameters include timeout and connection settings unusual for node creation.

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

Conciseness3/5

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

The description is brief (4 words plus parenthetical), but the '(Compatibility tool)' clause consumes space without delivering usable information. Front-loading is correct, but the overall brevity is inappropriate given the lack of schema documentation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Inadequate for a tool with two undocumented parameters and no output schema. In a complex domain with 100+ sibling tools, the description provides no context about what a GridMap is (3D tile system), how it differs from TileMap, or what the return value represents.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% (no descriptions for timeoutMs or autoConnect). The description completely fails to compensate, providing no information about these parameters, their units (milliseconds implied by name but not confirmed), or their relationship to GridMap node creation.

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 states the specific action (Create) and resource type (GridMap node), distinguishing it from generic siblings like add_node. However, the '(Compatibility tool)' parenthetical is unexplained, leaving ambiguity about whether this creates a legacy/deprecated node type or requires special handling.

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

Usage Guidelines1/5

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

No guidance provided on when to use this versus add_node or other node creation tools. The 'compatibility' label suggests specific usage constraints, but none are explained. No alternatives or prerequisites mentioned.

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