Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_navigation_path

Calculate navigation paths to targets in Godot game engine projects, enabling AI assistants to determine routes for character movement and pathfinding between locations.

Instructions

Calculate navigation path to target. (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_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, yet the description discloses no behavioral details: whether the operation is read-only or stateful, what format the returned path takes, error conditions, or the implications of the timeout/autoConnect parameters.

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?

Extremely brief and front-loaded, consisting of just two fragments. While conciseness is technically achieved, the extreme brevity contributes to under-specification rather than clarity.

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?

Severely incomplete for even a 2-parameter tool. The disconnect between the description's 'target' and the actual schema parameters, combined with zero parameter documentation and no output schema description, 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?

With 0% schema description coverage, the description fails entirely to compensate. It references a 'target' that does not appear in the schema (despite additionalProperties being true), and omits explanation of the actual parameters timeoutMs and autoConnect.

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?

States the basic action (calculating a navigation path) but leaves the 'target' concept undefined. Does not differentiate from sibling tools like 'navigate_to' or 'move_to' which likely execute rather than calculate paths.

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?

Provides only the cryptic parenthetical '(Compatibility tool)' which hints at legacy usage but offers no explicit guidance on when to use this versus alternative navigation tools or what compatibility scenarios require it.

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