Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_navigation_layers

Configure Godot navigation layers to control AI pathfinding by defining which walkable surfaces specific agent types can access.

Instructions

Set navigation layers. (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": "set_navigation_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2/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 burden but offers minimal behavioral context. '(Compatibility tool)' hints at backward compatibility usage but fails to explain what gets modified (project settings? scene nodes?), the purpose of 'additionalProperties: true', or what successful invocation returns.

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), this is severe under-specification rather than efficient conciseness. The parenthetical '(Compatibility tool)' consumes space without providing actionable information, and no sentence explains the tool's actual mechanics.

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?

Completely inadequate given zero schema coverage, missing output schema, and 'additionalProperties: true' suggesting complex parameter requirements. The description explains neither the navigation layer concept nor the compatibility context, leaving critical gaps for agent operation.

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 coverage is 0% for both 'timeoutMs' and 'autoConnect', yet the description provides no compensation. Critically, it fails to document what properties are expected via 'additionalProperties: true', leaving the agent with no guidance on required inputs.

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 action ('Set') and resource ('navigation layers'), providing a basic verb+resource pairing. However, it fails to differentiate from sibling navigation tools like 'setup_navigation_region' or 'bake_navigation_mesh', and '(Compatibility tool)' is too vague to clarify scope.

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?

No guidance provided on when to use this tool versus siblings like 'setup_navigation_agent' or 'get_navigation_info'. No prerequisites, side effects, or workflow context is mentioned.

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