Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

wait_for_node

Wait for nodes to appear in Godot scenes before executing commands. Set timeout limits to handle asynchronous loading in automated game development workflows.

Instructions

Wait for node to appear. (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": "wait_for_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to explain blocking vs. polling mechanics, return values, failure modes on timeout, or what 'Compatibility tool' implies for behavior. It only states the high-level intent.

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 extremely concise (6 words plus a parenthetical) and front-loaded with the action. However, it approaches under-specification given the lack of schema documentation and annotations; the brevity leaves critical gaps rather than efficiently conveying essential information.

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?

Given the tool has 2 undocumented parameters, no output schema, and no annotations, the description is insufficiently complete. It fails to explain return values, error handling, or the significance of the 'Compatibility' designation, leaving the agent with minimal context for invocation.

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?

The input schema has 0% description coverage, yet the description fails to compensate by explaining the two parameters (timeoutMs and autoConnect). While timeoutMs implies milliseconds, the description doesn't clarify the units, defaults, or what 'autoConnect' connects to.

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 states a specific action ('Wait') and resource ('node'), distinguishing it from sibling tools like add_node, delete_node, or find_nodes_by_type. However, it lacks specificity about what 'appear' means (e.g., added to scene tree, becomes visible) and the cryptic '(Compatibility tool)' qualifier is 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?

The description provides no guidance on when to use this tool versus alternatives like find_nodes_by_type or get_game_scene_tree. The '(Compatibility tool)' parenthetical hints at specific usage constraints but is too vague to constitute actionable guidance.

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