Skip to main content
Glama
Beckett — MCP for Godot

Beckett — MCP for Godot

by beckettlab

wait_for_node

Read-only

Block until a node appears in the RUNNING game (by path/name) or timeout. Use after play_scene to sync before you read the game (or, in Full, drive it).

Instructions

Block until a node appears in the RUNNING game (by path/name) or timeout. Use after play_scene to sync before you read the game (or, in Full, drive it).

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": {
      "path": "<path>"
    },
    "name": "wait_for_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
timeout_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.12.1
  2. Removedv1.10.0
  3. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuine value by disclosing that the call blocks and is bounded by a timeout, but it omits what happens on timeout (error vs. false return) and what the default timeout is — material for a blocking call.

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?

Two short sentences, front-loaded with the blocking behavior and followed by the usage cue. The parenthetical '(or, in Full, drive it)' is slightly cryptic and costs a bit of clarity, but there is no filler.

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 blocking tool with no output schema, the description covers purpose, ordering, and the timeout bound. It is still incomplete on the failure mode (timeout result), default timeout, and whether the node must match exactly by path or name — details an agent needs to handle the call correctly.

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 coverage is 0%, so the description must carry the parameter burden. It conveys that the required argument identifies a node 'by path/name' and that a timeout exists, but leaves the path-vs-name ambiguity unresolved and never states timeout_ms units or default, so the two undocumented params are only partially compensated for.

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?

States a specific verb and resource ('Block until a node appears in the RUNNING game') plus the terminating condition (timeout). The RUNNING-game qualifier usefully scopes it away from editor-tree siblings like find_nodes or get_scene_tree, though it does not explicitly name the closest alternative, wait_until.

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

Usage Guidelines4/5

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

'Use after play_scene to sync before you read the game' gives a concrete triggering context and names the sibling that precedes it. It stops short of stating when to prefer this over wait_until or get_play_state, so the routing is clear but not exhaustive.

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