Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

update_property

Set or change a property value on a node in the currently open Godot scene by specifying its node path, property name, and new value.

Instructions

Set a property value on a node in the currently open scene.

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": "update_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesNew value for the property
propertyYesName of the property to update
node_pathYesPath of the node

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 behavioral burden. It does not state what happens on an invalid node path or property name, whether the change is undoable, whether it works in edit vs. play mode, or what is returned; 'Set' is the only hint that this mutates state.

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 well-formed sentence with the operation and scope front-loaded and zero filler. It is lean to the point of under-specification, but no wording is wasted.

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-parameter mutation tool with no annotations and no output schema, the description should cover error conditions, undo behavior, and required scene state; none of these are addressed, leaving meaningful gaps even though the input schema is fully documented.

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 coverage is 100%, with node_path, property, and value each described in the schema, so the baseline of 3 applies. The description adds no format hints (e.g., path syntax or accepted value types) beyond what the schema already provides.

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 value') and scopes it to 'a node in the currently open scene', so the agent knows exactly what operation is performed. It stops short of contrasting with close siblings such as batch_set_property or set_game_node_property, so the agent must infer the distinction.

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?

The 'currently open scene' phrasing implies the required context but there is no explicit when-to-use guidance, no prerequisite (scene must be open, node must exist), and no pointer to the batch alternative for multi-property work.

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