Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

setup_navigation_agent

Add a NavigationAgent2D or NavigationAgent3D node to a chosen parent in the Godot scene and override its properties to set up AI pathfinding.

Instructions

Add a NavigationAgent3D/2D node 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_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
propertiesNoNavigationAgent 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 supplied, so the description carries the full behavioral burden, yet it only says a node is added. It does not disclose whether the node is selected or attached to the edited scene, what happens if parent_path is omitted, whether the operation is undoable, or whether navigation map registration occurs automatically.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity borders on under-specification for a mutation tool that creates a scene node.

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?

With no annotations, no output schema, and both parameters optional, the description should clarify defaults, the resulting state, and what is returned. It leaves all of that unstated, which is thin for a tool that mutates the scene tree.

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 coverage is 100%, with both properties (properties overrides and parent_path) documented in the schema itself, so the baseline is 3. The description adds nothing about either parameter, such as what defaults are used for a missing parent path or which NavigationAgent properties are honored.

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 names a concrete verb ("Add") and a concrete resource ("NavigationAgent3D/2D node"), so an agent can tell what gets created and that both 2D and 3D variants are supported. It does not distinguish this from siblings such as add_node or setup_navigation_region, which likely also place nodes in the scene.

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 guidance on when to use this versus add_node, batch_add_nodes, or setup_navigation_region, and no prerequisites or exclusions are stated. The agent must infer the use case from the tool name alone.

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