Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

select_node

Select a node in the Godot editor scene tree panel by providing its node path, so you can focus the editor on a specific node during AI-driven game development.

Instructions

Select a node in the editor scene tree panel.

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

Input Schema

NameRequiredDescriptionDefault
node_pathYesPath of the node to select

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden of behavioral disclosure and provides almost none. It does not say whether selection is a harmless UI state change, what happens if node_path does not resolve, whether the tree expands or scrolls to reveal the node, or whether prior selection is lost. Only the implied non-destructiveness of "select" gives any behavioral signal.

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?

A single short sentence with the action front-loaded and no filler. It is efficient, though its brevity is partly the cause of the missing context rather than pure economy.

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 one-parameter UI selection tool with no output schema, the definition is minimally sufficient to attempt a call. It is incomplete regarding failure behavior and return value, and with zero annotation coverage those gaps are not filled elsewhere.

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 description coverage is 100%, so node_path is already documented as "Path of the node to select", making 3 the baseline. The description adds no format detail such as whether the path is slash-delimited, root-relative, or an absolute scene path, so it does not improve on the schema.

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 gives a specific verb ("Select") and resource ("a node") scoped to "the editor scene tree panel", which usefully distinguishes an editor-side UI selection from game-side node tools. It stops short of clarifying how this differs from the sibling focus_node, leaving some ambiguity for an agent choosing between them.

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?

There is no guidance on when to use this rather than focus_node or get_node_properties, nor any stated preconditions such as the node needing to exist or the panel needing to be open. The agent must infer the usage context entirely from the name and one-line purpose.

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