Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

set_particle_property

Sets a single property on a Godot particle node using its node path, property name, and new value to adjust particle behavior in AI-driven game development.

Instructions

Set a single property on a particle node.

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_particle_property"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesProperty value
propertyYesProperty name
node_pathYesPath to the particle node

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure and delivers almost none. It does not say whether the property must already exist, whether the change is persistent or undoable, what happens on an invalid path, or whether a value is returned.

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 with the resource and operation front-loaded and no filler. It is efficient, though its brevity reflects under-specification rather than disciplined trimming.

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 mutation tool with zero annotations, no output schema, and ambiguous siblings, this description is too thin. It leaves the agent without safety, persistence, or failure-mode context needed to call it correctly.

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 are documented structurally, and the description adds no format, path syntax, or value-type guidance beyond that. The baseline of 3 applies when the schema does the heavy lifting.

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

Purpose3/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 particle node") and the word "single" hints at a batch alternative, but it never says which properties are valid or how it differs concretely from set_particle_material or batch_set_property. An agent can guess the general intent but cannot confidently distinguish it from several siblings.

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 when-to-use guidance, no stated prerequisites, and no reference to alternatives such as batch_set_property for multiple values or set_particle_material for material properties. The agent must infer routing entirely from tool names.

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