Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

apply_particle_preset

Apply a named particle effect preset to a particle node to quickly set up effects such as fire, smoke, or explosions.

Instructions

Apply a named particle effect preset to 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>",
      "preset": "<preset>"
    },
    "name": "apply_particle_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetYesPreset name (e.g. fire, smoke, explosion)
node_pathYesPath to the particle node

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?

With no annotations, the description carries the full burden of behavioral disclosure. It does not say whether applying a preset overwrites existing particle settings, whether it is reversible, what permissions or editor state are required, or what happens if the preset name is invalid.

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. It is efficient, though its brevity borders on under-specification for a mutation tool.

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 and no output schema, the definition is thin. An agent cannot tell what the tool destroys or replaces, nor what state change to expect in the particle node after the call.

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 both node_path and preset are already documented, including the preset examples (fire, smoke, explosion). The description adds no syntax, format, or path-resolution detail beyond the schema, which is the expected baseline 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.

Purpose4/5

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

The description states a specific verb and resource: applying a named particle effect preset to a particle node. This distinguishes it from the more general set_particle_property, but it doesn't explicitly differentiate from siblings like apply_theme_to_node or get_particle_info, leaving scope comparison to the reader.

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 guidance on when to use this tool versus alternatives such as set_particle_property or get_particle_info, and no prerequisites are mentioned. The single sentence gives only implied usage.

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