Skip to main content
Glama
Sign In
Godot MCP

Godot MCP

by KeeVeeG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

navigate_to

Move a specified node to a target position using pathfinding in a running Godot game.

Instructions

🔴 Game must be running. Navigate a node to a target position using pathfinding

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": {
      "path": "<path>",
      "target": "<target>"
    },
    "name": "navigate_to"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesNode path to navigate (must have NavigationAgent3D)
targetYesTarget position [x, y, z]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, and the description fails to disclose behavioral traits such as whether navigation is synchronous or asynchronous, what happens upon failure, or if the operation is destructive. The requirement for a NavigationAgent3D is only in the parameter schema, not highlighted.

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?

The description is a single sentence with a prominent prerequisite emoji. Every word is functional with no redundancy.

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?

There is no output schema, and the description does not explain what the tool returns or whether it waits for movement completion. Additional context about the navigation agent and potential outcomes is missing for a tool that triggers movement.

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 parameter descriptions already define 'path' and 'target'. The main description adds no new parameter information beyond restating the types. Baseline 3 is appropriate.

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 'Navigate' and resource 'a node', and specifies the method 'using pathfinding'. It distinguishes itself from the sibling 'navigate_character' by focusing on nodes.

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

Usage Guidelines3/5

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

The description includes a prerequisite '🔴 Game must be running.' but does not provide guidance on when to use this tool versus alternatives like 'navigate_character', 'move_to', or 'find_navigation_path'.

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