Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

set_game_node_property

Set a property on a node in the running game to apply live edits without restarting. Provide the node path, property name, and new value for immediate runtime changes.

Instructions

Set a property on a node in the running game (live edit).

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>",
      "value": "<value>"
    },
    "name": "set_game_node_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesNew value
propertyYesProperty name
node_pathYesNode path in the running game

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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 discloses only that the edit is live. It says nothing about whether changes persist or are transient, whether permissions or a paused game are required, what happens if the node path or property is invalid, or whether the operation can fail destructively.

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 short sentence, front-loaded with the action and scoped by the parenthetical. It contains no padding, though the terseness leaves gaps rather than filling them.

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?

For a three-required-parameter mutation tool with no annotations and no output schema, the description is too thin. It omits failure modes, persistence semantics, and any indication of what a successful call returns or changes.

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 (node_path, property, value) are already documented in the schema. The description adds no format hints, path syntax, or value-type guidance beyond that.

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 (set a property on a node) and adds a scoping qualifier, 'in the running game (live edit)', that separates it from file/scene-editing operations. It does not explicitly distinguish itself from the sibling batch_set_property, which is the most obvious confusion risk.

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 phrase 'in the running game (live edit)' implies the context in which this tool applies, but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as batch_set_property for multiple 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