Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_game_scene_tree

Retrieves the scene tree from a running Godot game so you can inspect the node hierarchy and understand the game's structure.

Instructions

Get the scene tree of the running game.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does not say whether the call fails when no game is running, whether it is a read-only snapshot, how deep the tree goes, or whether node properties are included — all behaviors an agent needs before invoking it mid-session.

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. It is efficient, though the flat phrasing leaves no structure for scope or precondition to sit in.

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 zero-parameter read tool this is close to adequate, but there is no output schema, so the description is the only place a reader could learn what the returned tree looks like or under what runtime state it is valid. Those gaps matter given the several overlapping node/scene siblings.

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 nothing for the description to disambiguate; the baseline applies. No parameter-level meaning is missing because none exists.

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 and resource ('Get the scene tree') plus a scope qualifier ('of the running game') that meaningfully separates it from the editor-side sibling get_scene_tree. It stops short of naming that sibling explicitly, so the differentiation is inferred from the phrase 'running game' rather than stated.

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?

The 'running game' qualifier implies the runtime context (the game must be playing), but the description never states that precondition outright nor contrasts with get_scene_tree, get_current_scene, or list_game_nodes_by_type. An agent must infer when this tool is the right pick.

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