Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

set_particle_material

Configure ParticleProcessMaterial properties on a specified particle node to control emitted particle appearance and behavior.

Instructions

Set the process material properties 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>"
    },
    "name": "set_particle_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesPath to the particle node
propertiesNoParticleProcessMaterial property values

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 disclosure burden for a mutation tool. It says nothing about whether the supplied properties merge with or replace the existing material, whether the change is undoable, what happens if node_path is invalid or points at a non-particle node, or whether the node must already have a process material assigned.

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 no filler or redundancy. It is efficient, though its brevity is partly under-specification rather than tight writing.

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 no annotations, no output schema, and a nested free-form properties object, the description is too thin. An agent still lacks merge/replace semantics, the expected property key format, and failure behavior — the exact things the structured fields do not provide.

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% (both parameters documented), so the schema already explains node_path and the properties object. The phrase "process material" does slightly narrow what belongs in the properties dict, but no format, key naming, or partial-update semantics are added beyond the schema — the expected baseline of 3.

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 states a specific verb ("Set") and resource ("process material properties on a particle node"), which is more precise than a generic property setter. It does not, however, distinguish itself from close siblings such as set_particle_property, set_material_3d, or apply_particle_preset, so an agent cannot tell from the text alone why it would pick this tool over those.

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 mention of prerequisites (e.g. the node must be a particle node with a ParticleProcessMaterial), and no reference to alternatives despite several plausible siblings. The agent must infer the entire selection context from the name and schema.

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