Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

find_game_node

Locate a node by name in a running Godot game's scene tree, enabling targeted scene inspection and AI-driven commands without manual navigation.

Instructions

Find a node by name in the running game scene tree.

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

Input Schema

NameRequiredDescriptionDefault
nameYesNode name to search for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden but only mentions the search scope ('running game scene tree'). It does not disclose read-only behavior explicitly, duplicate-name handling, error behavior when not found, or what is returned.

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 description is a single front-loaded sentence with no wasted words. It is appropriately sized for a simple one-parameter find tool.

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?

There is no output schema and no annotations, so the description should clarify return semantics and duplicate handling. It omits what happens when multiple nodes share the name, what is returned, and whether the game must be running as a precondition.

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 100%, so the 'name' parameter is fully documented by the schema. The description adds only that the name is used to find a node in the running game scene tree, which is minimal beyond the schema.

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 states a specific verb ('Find'), resource ('node'), and scope ('by name in the running game scene tree'). It distinguishes itself from sibling tools such as find_nodes_by_type and get_game_scene_tree by specifying lookup by name within the active scene tree.

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

Usage Guidelines3/5

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

Usage is only implied: call this when you know a node's name and need to locate it in the running scene. The description gives no explicit when-to-use guidance, exclusions, or alternative routing compared to 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