Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

find_nearby_nodes

Locate nearby game objects by position in Godot scenes to identify nodes near specific coordinates and enable spatial scene editing.

Instructions

Find nearby nodes by 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": "find_nearby_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It fails to disclose what 'nearby' means (units, measurement method), what the return value contains, or how to interpret the results. The existence of 'timeoutMs' and 'autoConnect' parameters suggests network or async behavior that the description completely ignores.

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

Conciseness3/5

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

The description is brief (one sentence + fragment), but the '(Compatibility tool)' fragment wastes space without adding actionable information. Given the lack of schema documentation, the description is too terse rather than appropriately concise.

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?

With 0% schema coverage, no annotations, no output schema, and only 2 optional parameters, the tool requires more descriptive context. The description fails to explain the spatial query mechanism, the purpose of the timeout, or what 'autoConnect' connects to, leaving significant operational gaps.

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

Parameters2/5

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

Schema description coverage is 0%, requiring the description to compensate. It mentions 'by position' implying coordinates are required, but these are not defined in the schema properties (only additionalProperties: true). It fails to explain 'timeoutMs' or 'autoConnect', leaving critical behavioral parameters undocumented.

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 (find nodes) and criterion (by position), but 'nearby' is undefined (distance? radius? viewport?) and '(Compatibility tool)' is cryptic without explanation. It minimally distinguishes from sibling 'find_nodes_by_type' via the spatial aspect, but lacks specificity.

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 when-to-use guidance or alternatives. The parenthetical '(Compatibility tool)' suggests a specific use case but fails to explain what compatibility it provides or when to prefer this over other find_* siblings.

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