Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

monitor_property

Track a node property over a set duration in the running game and return sampled values for debugging or analysis.

Instructions

Monitor a node property over time in the running game and return sampled values.

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>",
      "property": "<property>"
    },
    "name": "monitor_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
durationNoDuration to monitor in seconds (default: 1.0)
propertyYesProperty name to monitor
node_pathYesNode path in the running game

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/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 behavioral burden, and it leaves the most consequential trait undisclosed: whether the call blocks for the entire 'duration' before returning or returns immediately. Sampling frequency, behavior when the node path or property does not exist, and any permission requirements are also unstated. The only real disclosure is that it targets the running game and yields multiple sampled values rather than one.

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; the purpose and the key qualifier ('in the running game') come first. It is efficient, though its brevity is partly the cause of the behavioral gaps noted above rather than pure economy.

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?

With three well-documented parameters and no output schema, the description does at least indicate the return is sampled values over time. However, for a tool that runs against a live game for a configurable duration, the absence of any statement about blocking behavior or sampling cadence leaves an agent unable to predict the call's cost or timing.

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%, so all three parameters including the duration default are already documented in the schema. The description's 'over time' and 'sampled values' contextualize what duration means without adding format, units, or bounds beyond the schema. Baseline 3 applies.

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 names a specific verb and resource ('Monitor a node property'), plus a scope qualifier ('over time in the running game') that separates it from the surrounding setter siblings such as set_game_node_property and update_property. It does not explicitly name an alternative, but the verb+resource pairing 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'over time' and 'return sampled values' suggest this is for observing changing values rather than a one-shot read or a write. There is no statement of when NOT to use it, no named alternative (e.g. assert_node_state or a direct getter), and no prerequisite such as the game needing to be in play mode.

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