Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

batch_set_property

Set the same property on multiple Godot nodes at once by passing a list of node paths, a property name, and a value, avoiding repetitive single-node edits.

Instructions

Set the same property on multiple nodes at once.

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_paths": "<node_paths>",
      "property": "<property>",
      "value": "<value>"
    },
    "name": "batch_set_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesValue to set on all nodes
propertyYesProperty name
node_pathsYesList of node paths

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 exist, so the description carries the full burden, yet it says nothing about atomicity or partial failure (what happens if some node_paths are invalid), what the return value reports per node, permissions, or reversibility. For a multi-target mutation this is a substantial gap.

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 zero filler keeps the core action immediately visible. It is terse rather than padded, and the brevity is only a problem insofar as content is missing, not because of wasted words.

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 bulk mutation with no annotations and no output schema, the description should at least characterize failure behavior and the shape of the result. Nothing beyond the basic action is covered, so an agent cannot predict what happens when a path is bad.

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 all three parameters are already documented in the schema. The description does add the semantic that a single value is applied uniformly across the node list, but offers no format details for node paths or property names beyond that; 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: 'Set the same property on multiple nodes at once.' That cleanly separates it from single-target setters like set_game_node_property or set_particle_property, though it does not name any sibling explicitly.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The phrase 'at once' only implies that this is the bulk-efficiency path over repeated single-node setting, leaving the agent to infer that tradeoff.

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