Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

navigate_to

Direct game actors to target coordinates in Godot projects using AI-assisted navigation. Controls character and object positioning through the Godot MCP Bridge.

Instructions

Navigate actor to position. (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": "navigate_to"
  }
}

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?

With no annotations provided, the description carries full disclosure burden but offers minimal behavioral context. It does not explain whether navigation uses pathfinding or teleportation, what the timeout encompasses, or what 'autoConnect' connects to. The 'Compatibility' label lacks elaboration.

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 at two short sentences. Information is front-loaded, but 'Compatibility tool' acts as unexplained jargon rather than useful context. Brevity crosses into under-specification given the schema complexity and missing parameter documentation.

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?

Inadequate for a tool with 0% schema coverage and no annotations/output schema. The description omits the parameter specification mechanism (additionalProperties), return value behavior, and the nature of the 'actor' being navigated. Requires significant external knowledge to use correctly.

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?

Critical mismatch: the description references a 'position' parameter not defined in the schema (though additionalProperties allows it), while completely ignoring the two actual defined parameters (timeoutMs and autoConnect). With 0% schema coverage, the description fails to compensate by explaining parameter semantics, formats, or requirements.

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 (navigate actor to position) with a specific verb and resource, but fails to distinguish from sibling tool 'move_to' which likely performs a similar function. The '(Compatibility tool)' label is present but unexplained.

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 no explicit guidance on when to use this tool versus alternatives like 'move_to' or 'setup_navigation_agent'. The 'Compatibility tool' parenthetical hints at legacy usage but does not clarify when this should be preferred over newer options.

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