Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_game_node_properties

Retrieves properties of a running Godot game node from its node path, enabling AI-driven inspection and debugging of live scene data.

Instructions

Get properties of a node in the running game.

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

Input Schema

NameRequiredDescriptionDefault
node_pathYesNode path in the running game

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?

No annotations are supplied, so the description carries the full disclosure burden and does not meet it. It never confirms the operation is read-only, does not say whether the game must be running or paused, and does not state what happens if node_path does not resolve.

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 written, though the terseness is part of why behavioral detail is missing rather than a virtue in itself.

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 read tool with no output schema, the description should at minimum indicate what a 'property' set looks like or how large it may be. It leaves the return shape and node-path resolution semantics entirely undocumented.

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% for the single required parameter, so the baseline applies. The description repeats the parameter's meaning ('node in the running game') without adding format details such as whether the path is absolute, slash-delimited, or relative to the scene root.

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 pairs a specific verb ('Get') with a specific resource ('properties of a node'), and adds the qualifying scope 'in the running game', which hints at runtime vs. editor state. That qualifier is the only thing separating it from the sibling get_node_properties, and it is never made explicit.

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 stated when-to-use, when-not-to-use, or prerequisite context. An agent must infer from the phrase 'in the running game' that this tool requires a live game session, and it gets no guidance on choosing between this and the nearly identically named get_node_properties.

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