Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_game_node_properties

Retrieve live property values from running Godot game nodes for runtime inspection and debugging.

Instructions

Read runtime node properties. (Compatibility tool)

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

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations provided, the description carries full disclosure burden but offers minimal behavioral context. The 'runtime' hint suggests it targets a running game instance, and 'Compatibility tool' cryptically hints at legacy status, but it omits connection requirements, caching behavior, and return value structure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely brief at two phrases, but the '(Compatibility tool)' tag consumes space without adding actionable information. The lack of parameter or output documentation makes this under-specification rather than efficient precision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Inadequate for a complex game-engine integration tool with no output schema or annotations. The description omits critical context: how runtime connection is established, what the returned property format looks like, and why this is labeled a compatibility tool.

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

Parameters1/5

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

Completely fails to compensate for 0% schema description coverage. The description mentions nothing about timeoutMs (connection timeout?), autoConnect (auto-connection behavior?), or the significance of additionalProperties: true (which likely carries the actual node property requests).

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 the core action ('Read') and target ('runtime node properties'), distinguishing it from siblings like get_node_properties via the 'runtime' qualifier. However, the '(Compatibility tool)' parenthetical is unexplained and doesn't explicitly clarify when to prefer alternatives like monitor_properties.

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?

Provides no guidance on when to use this tool versus siblings such as get_node_properties (editor-time) or batch_get_properties, nor does it explain the prerequisites for accessing 'runtime' properties (e.g., requiring an active game connection).

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