Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

setup_navigation_region

Adds a NavigationRegion2D or 3D with a NavigationMesh to a Godot scene, letting you set the parent node and override region properties.

Instructions

Add a NavigationRegion3D/2D with a NavigationMesh to the scene.

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": "setup_navigation_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
propertiesNoNavigationRegion property overrides
parent_pathNoParent node path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It does not say whether the navigation mesh is generated or required to exist, whether the operation is reversible, what happens to an existing NavigationRegion, or what the tool returns after adding the region.

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

Conciseness4/5

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

The description is a single front-loaded sentence with no wasted wording. It is appropriately sized, though its brevity contributes to gaps covered in other dimensions rather than being a structural flaw.

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?

For a mutation tool with no annotations, no output schema, and a nested 'properties' object, the description is too thin to be complete. It omits prerequisites, side effects, and basic behavioral context an agent would need before invoking it.

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 the schema already documents both parameters and the baseline is 3. The description does not add meaning beyond the schema for 'properties' or 'parent_path', so it neither compensates nor improves parameter understanding.

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 a specific verb ('Add') and resource ('NavigationRegion3D/2D with a NavigationMesh') clearly enough for an agent to distinguish it from siblings like setup_navigation_agent and bake_navigation_mesh. It is clear but does not explicitly differentiate itself from those alternatives.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of when not to use this tool versus bake_navigation_mesh or setup_navigation_agent. The intent is only implied by the tool name and the phrase 'to the scene'.

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