Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

bake_navigation_mesh

Bake a NavigationRegion3D node's navigation mesh from a specified node path, enabling AI-driven Godot scene navigation setup.

Instructions

Bake the navigation mesh for a NavigationRegion3D node.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "node_path": "<node_path>"
    },
    "name": "bake_navigation_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesPath to the NavigationRegion3D

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 carries the full burden, yet it does not say whether baking is synchronous or async, whether it mutates the saved scene or only runtime data, whether it is undoable, or how failure (invalid path, unconfigured region) is reported. The single clause adds nothing beyond the operation's name.

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?

One front-loaded sentence with zero filler or redundancy. It is tight, though the brevity borders on under-specification for an operation with no annotations backing it.

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/compute tool with no annotations and no output schema, the definition omits what the agent needs to invoke it confidently: prerequisites, whether results are persisted, and what a successful bake yields. It is technically callable but not complete.

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 single node_path parameter is already documented as 'Path to the NavigationRegion3D'. The description adds no format hints, path syntax, or constraints beyond that, which is the expected baseline when the schema does the work.

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?

States a specific verb ('Bake') and resource ('navigation mesh') scoped to a NavigationRegion3D node, which is enough to separate it from siblings like setup_navigation_region or get_navigation_map_info. It stops short of naming any sibling explicitly, so differentiation relies on the agent's inference from the resource names.

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?

The description gives no when-to-use guidance, no prerequisites (e.g. the region must already exist and be configured in the scene tree), and no indication of when re-baking is needed versus when it is wasteful. Usage is only implied by the resource name.

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