Skip to main content
Glama
Beckett — MCP for Godot

Beckett — MCP for Godot

by beckettlab

find_nodes

Read-only

Locate live nodes in a running Godot game by class or name and return their paths for runtime property inspection and modification.

Instructions

Find LIVE nodes in the RUNNING game by type and/or name; returns their paths to feed into runtime_get_property (in Full also runtime_call and runtime_set_property). 'class' matches native classes AND custom class_name scripts (is_class alone misses custom nodes, which read as @Node@NN). name=substring on the node name. path=scope root (default scene root). recursive=true. max=cap (default 100).

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_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNo
nameNo
pathNo
classNo
recursiveNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare a safe read, so credit goes to added context: the results are live runtime nodes (implying the game must be running), there is a default cap of 100, and the default scope is the scene root. It stops short of saying what happens when the game isn't running or how truncation is signalled.

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?

Front-loaded with purpose and return value, then a compact per-parameter gloss. The telegraphic style is dense but every clause carries information an agent needs.

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

Completeness4/5

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

With no output schema, the description does the right thing by saying it returns paths. Parameter behavior is fully covered. The remaining gap is failure/edge behavior (game not running, cap exceeded) for a five-parameter tool.

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

Parameters5/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 all meaning — and it does, documenting every one of the five parameters: class semantics, name as substring, path as scope root with its default, recursive=true, and max as a cap defaulting to 100.

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?

States a specific verb and resource ('Find LIVE nodes in the RUNNING game') plus the return value (paths). The 'LIVE/RUNNING' framing distinguishes it from editor-tree siblings like get_scene_tree and get_remote_tree.

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?

Explicitly names the downstream consumers (runtime_get_property, and in Full runtime_call/runtime_set_property), which tells the agent when to reach for this tool. Also clarifies the 'class' vs is_class distinction and how custom scripts appear. No explicit when-not guidance, keeping it below a 5.

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