Godot AI

Overview Schema Source Related Servers Discussions Admin

Node Set Property

node_set_property

Set a Godot scene node's property with automatic type coercion for Vector2, Color, NodePath, and resources. Check exact property names with node_get_properties first.

Instructions

Set a property on a node.

Verify the property name first — call node_get_properties (or read godot://node/{path}/properties) to confirm the exact name and type before writing. Guessing common Godot names often fails with PROPERTY_NOT_ON_CLASS because Godot's actual properties differ from intuition (e.g. Camera3D uses fov/current, not field_of_view; Sprite2D uses texture, not image; Node3D uses position/rotation/scale, not transform.origin).

Coerces value to the property's type:

Vector2/Vector3: dict with x/y/z keys.
Color: dict {r,g,b,a} or hex string ("#ff0000").
NodePath: string ("../Other/Node").
Resource: res:// path string (loads + assigns); null/"" clears. {"__class__": "BoxMesh", ...} creates a built-in resource owned by this property. After scene_save it is serialized in-place as a [sub_resource] inside the .tscn; it is not a reusable .tres. For sharing, first call resource_manage(op="create", params={"type": "BoxMesh", "properties": {...}, "resource_path": "res://meshes/box.tres"}), then pass that res:// path here (or use resource_manage(op="assign")).
StringName: plain string. Array/Dictionary: JSON list/object.

Input Schema

TableJSON Schema

Name	Required	Description
`path`	Yes	Scene path relative to the edited scene root (e.g. "/Main/Camera3D"), NOT runtime "/root/..." paths.
`value`	Yes	New value. Pass null (or "" for resources) to clear.
`property`	Yes	Property name (e.g. "fov", "position", "mesh"). Must match Godot's exact identifier — introspect with ``node_get_properties`` if unsure rather than guessing.
`scene_file`	No	Optional editor-scene guard.
`session_id`	No	Optional Godot session to target. Empty = active session.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Addedv3.1.4Aug 10, 2026
Removedv3.0.7Jul 26, 2026
First observedv2.9.1Jul 11, 2026

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden, and it delivers: it discloses coercion behavior per type, the PROPERTY_NOT_ON_CLASS failure mode, serialization semantics for built-in resources, and clearing via null/"". This far exceeds a simple mutation warning.

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?

The description is long, but it is front-loaded with the core action and verification instruction, then organized as a bulleted coercion list. The resource-sharing detail is dense but earns its place because that is where agents commonly fail.

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

Completeness5/5

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

Given the tool's complexity and the availability of an output schema plus fully described parameters, the description covers every hard part: property-name discovery, type coercion, resource lifecycle, and sibling routing. No critical operational gap remains.

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

Parameters5/5

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

Schema coverage is 100%, but the description still adds substantial meaning beyond the schema's type definitions. It explains the exact accepted shapes for Vector2/3, Color, NodePath, Resource, StringName, Array, and Dictionary, which the schema alone does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Set a property on a node,' a specific verb and resource with no ambiguity about the action. It also names complementary siblings like node_get_properties and resource_manage, making clear that this tool is the write operation, not a reader or resource manager.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

It explicitly tells the agent to verify property names with node_get_properties before writing and warns against guessing, which is concrete when-to-use guidance. It also provides an alternative resource_manage workflow for shared resources, clarifying when not to pass a raw dict directly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.