Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

set_navigation_layers

Sets the navigation layer bitmask on a navigation node, enabling control over which navigation layers the node participates in.

Instructions

Set the navigation layer bitmask on a navigation node.

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": {
      "node_path": "<node_path>",
      "layers": "<layers>"
    },
    "name": "set_navigation_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault
layersYesNavigation layer bitmask
node_pathYesNode path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden for a mutation tool. It does not say whether the bitmask replaces or merges with existing layers, whether a navigation mesh rebake is required for the change to take effect, or what permissions or failure modes exist.

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?

A single front-loaded sentence with no filler; the verb and target appear immediately. It is efficient, though its brevity is partly under-specification rather than disciplined concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter setter with a fully documented schema and no output schema, the core action is conveyed adequately. However, with zero annotations the description should explain the bitmask's effect on navigation behavior and whether the change takes effect immediately, which it omits.

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 both parameters are already documented as 'Navigation layer bitmask' and 'Node path'. The description merely repeats that framing and adds no bit semantics, valid ranges, or path format details beyond the schema, making the baseline 3 appropriate.

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

Purpose4/5

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

The description names a specific verb ('Set'), a specific resource ('navigation layer bitmask'), and a target ('a navigation node'), which is enough to distinguish it from the physics-layer sibling. It stops short of explicitly contrasting with set_physics_layers or get_collision_layers_info, so it is clear but not fully differentiated.

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?

There is no guidance on when to call this versus set_physics_layers or get_navigation_map_info, no preconditions, and no note about when not to use it. The agent must infer usage entirely from the name and schema.

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