Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_scene_tree

Retrieve the full scene tree structure of the currently open Godot scene to inspect node hierarchy and support AI-driven game development commands.

Instructions

Get the full scene tree structure of the currently open scene.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. It does disclose two useful traits: the result is 'full' (no filtering or depth limit) and scoped to the currently open scene (fails or returns nothing if none is open). It says nothing about output format, size expectations for large scenes, or freshness/caching.

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?

A single front-loaded sentence with no filler; the scope qualifier 'currently open scene' lands where it matters most. Nothing could be cut without losing meaning.

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 no-parameter, no-output-schema read tool this is close to sufficient, but the return shape (node hierarchy format, path vs. nested structure) is left entirely undefined and there is no annotation coverage to compensate. An agent knows what to call but not quite what it will get back.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. The description adds no misleading or extraneous parameter-like claims.

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?

Specific verb (get) plus a precisely scoped resource (full scene tree structure of the currently open scene). The phrase 'currently open scene' implicitly separates it from get_game_scene_tree, but the description never names that sibling, so differentiation relies on inference.

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: 'currently open scene' signals it works on the editor's open scene rather than a running game, which nudges an agent toward get_game_scene_tree for the latter. There is no explicit when-to-use statement, no mention of analyze_scene_complexity for summarized inspection, and no prerequisites noted.

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