Skip to main content
Glama

nav

Create navigation regions, agents, and links; bake navmeshes; and query 3D paths in Godot.

Instructions

导航操作。create_region: 创建 NavigationRegion3D(可选烘焙)。bake_mesh: 烘焙导航网格(耗时较长)。create_agent: 创建 NavigationAgent3D。set_params: 设置导航参数。create_link: 创建 NavigationLink3D。query_path: 查询 3D 导航路径。运行时操作,仅影响当前执行上下文。如需持久化,请编辑 .tscn 文件。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bakeNocreate_region: 是否立即烘焙导航网格(默认 false)
nameNocreate_region/create_agent/create_link: 节点名称
actionYes操作类型
paramsNoset_params: 导航参数(仅传入需要修改的字段)
parentNocreate_region/create_agent/create_link: 父节点路径(默认 root)
end_posNoquery_path: 终点 {x,y,z}
timeoutNobake_mesh 烘焙超时秒数(默认 120,大场景可调至 600)
positionNocreate_region: 位置 {x,y,z}
node_pathNobake_mesh/set_params: 目标节点路径
start_posNoquery_path: 起点 {x,y,z}
end_positionNocreate_link: 终点位置 {x,y,z}
project_pathNoGodot 项目目录路径(可选,默认使用 GODOT_PROJECT_PATH 环境变量或当前目录)
bidirectionalNocreate_link: 是否双向通行(默认 true)
load_autoloadsNo是否加载 Autoload 上下文(默认 true)
start_positionNocreate_link: 起始位置 {x,y,z}
target_positionNocreate_agent: 目标位置 {x,y,z}
avoidance_enabledNocreate_agent: 是否启用避障(默认 false)
navigation_regionNoquery_path: NavigationRegion3D 节点路径(可选)
path_desired_distanceNocreate_agent: 路径期望距离(默认 0.5)
target_desired_distanceNocreate_agent: 目标期望距离(默认 1.0)
Behavior4/5

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

The description discloses that operations are runtime-only (not persisted), that bake_mesh can take a long time, and that persistence requires editing .tscn. These are meaningful behavioral details not present in the annotations (readOnlyHint=false, destructiveHint=false), adding context beyond the structured data.

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

Conciseness5/5

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

The entire description is a single compact paragraph that front-loads the purpose, enumerates actions efficiently, and ends with a useful persistence caveat. No wasted words, and each phrase earns its place.

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?

Despite listing all actions, the description lacks information about return values (e.g., what query_path returns), error conditions, or how created nodes can be referenced later. With no output schema and a complex 20-parameter tool, this is insufficient for an agent to fully understand the tool's behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explains the action enum values, which the schema merely labels as '操作类型', adding crucial meaning. It also mentions bake_mesh's timeout sensitivity, complementing the timeout parameter. The schema covers the remaining parameters well, so the description adds value where the schema is weak.

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

Purpose5/5

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

The description clearly identifies the tool as a navigation operations dispatcher, listing six specific sub-actions (create_region, bake_mesh, create_agent, set_params, create_link, query_path) with one-line explanations. It distinguishes itself from sibling tools (physics, audio, scene) by being explicitly navigation-focused.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states that these are runtime operations affecting only the current execution context, and advises editing .tscn for persistence, providing an explicit when-not and alternative to the tool. It also implicitly guides when to use each sub-action via the enumerated list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wgt19861219/godot-mcp-enhanced'

If you have feedback or need assistance with the MCP directory API, please join our Discord server