Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_navigation_info

Retrieve navigation diagnostics from Godot game projects to debug pathfinding systems and analyze agent behavior.

Instructions

Get navigation diagnostics. (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": "get_navigation_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/5.0
Behavior2/5

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

With no annotations provided, the description carries full disclosure burden. 'Get' implies read-only, but the description doesn't clarify what 'diagnostics' are returned, whether this probes active navigation meshes, or what the 'autoConnect' parameter connects to. The 'Compatibility tool' label is opaque.

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

Conciseness2/5

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

While brief (4 words), the description is under-specified rather than efficiently concise. The parenthetical '(Compatibility tool)' consumes space without explanation, and critical information about parameters and return values is absent.

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?

Given zero schema descriptions, no annotations, no output schema, and two undocumented parameters, the description is inadequate. For a diagnostics tool likely returning complex navigation mesh or pathfinding data, the lack of return value documentation or parameter semantics leaves critical gaps.

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 description coverage is 0% for both 'timeoutMs' and 'autoConnect' parameters. The description completely fails to compensate for this gap by explaining what these parameters control (e.g., connection timeouts, automatic server connection) or their operational impact.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the basic action ('Get') and resource ('navigation diagnostics'), providing minimal viable purpose. However, it fails to define what 'navigation' encompasses (pathfinding, mesh status, agent states) or distinguish from sibling tool 'get_navigation_path', leaving scope ambiguous.

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 'get_navigation_path' or 'bake_navigation_mesh'. The parenthetical '(Compatibility tool)' hints at specific use cases but offers no explanation of what compatibility scenarios warrant its use.

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