Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_node_children

Retrieve the direct children of a specified Godot node to inspect scene hierarchy and identify child nodes by parent path.

Instructions

Get the direct children of a node.

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": "get_node_children"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesPath of the parent node

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, the description carries the full behavioral burden and supplies only the non-recursive scope implied by 'direct children'. It says nothing about what each child entry contains, ordering, behavior on an invalid or missing node_path, or whether hidden/internal nodes are included.

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 front-loaded sentence with no filler or redundancy. It is efficiently worded, though the brevity reflects under-specification rather than deliberate compression of rich content.

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?

This is a simple single-parameter read tool with no output schema and fully documented parameters, so the description is minimally adequate. It still leaves open what the returned children look like and how failures on a bad path behave, which an agent would want before calling.

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?

There is a single parameter with 100% schema description coverage, so the schema already defines node_path as the parent path and the baseline is 3. The description adds no format examples (path syntax, root notation) or constraints beyond what the schema provides.

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 (get) and resource (direct children of a node), and the word 'direct' meaningfully narrows scope so an agent can distinguish it from sibling readers like get_node_properties or get_node_signals. It stops short of naming an alternative explicitly, but the operation is unambiguous.

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 when-to-use guidance: no mention of when to prefer this over get_node_properties or get_node_signals, no prerequisites, and no note that it is non-recursive versus a recursive tree walk. The only usage hint is the implicit 'direct' scope, which the agent must infer.

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