Skip to main content
Glama
Sign In
Godot MCP Server Ultimate Edition

Godot MCP Server Ultimate Edition

by Dex865378
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

set_node_properties

Modify a node's properties in a Godot scene by specifying the node path and a key-value map of property values.

Instructions

Set properties of a node in a 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": {
      "projectPath": "<projectPath>",
      "scenePath": "<scenePath>",
      "nodePath": "<nodePath>",
      "properties": "<properties>"
    },
    "name": "set_node_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectPathYesPath to project
scenePathYesScene path
nodePathYesPath to target node, empty or root for scene root
propertiesYesKey-value map of properties to set

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided; description does not mention side effects, permissions, or whether properties are overwritten or merged.

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?

Single sentence, minimal and to the point, but could add context without significant bloat.

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?

No output schema; description omits return value, error handling, and validation details for a 4-parameter mutation tool.

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%, so baseline is 3. Description adds no extra meaning 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?

Description states verb 'set' and resource 'properties of a node', clearly distinguishing from sibling tools like 'get_node_properties' or 'bulk_set_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?

No guidance on when to use this versus alternatives like 'bulk_set_properties' or 'set_collision_layer_mask'.

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