Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

create_particles

Adds a GPUParticles3D or CPUParticles2D node to a Godot scene, enabling 2D or 3D particle effects with configurable name and parent path.

Instructions

Add a GPUParticles3D or CPUParticles2D node to the scene.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_particles"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNode name
type_2dNotrue = 2D particles, false = 3D particles (default)
parent_pathNoParent node path

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 supplied, the description carries the full burden of behavioral disclosure and does very little. It does not say where the node lands when parent_path is omitted, what name is assigned if name is omitted, whether the operation is reversible, or what the call returns (no output schema exists to fill that 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 no filler or redundancy. It is efficient, though the brevity stems partly from under-specification rather than disciplined compression.

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, zero required parameters, and no output schema, more is needed: the agent cannot tell what is returned or how defaults resolve. The description covers only the barest statement of intent.

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 the baseline is 3. The description does add one real semantic mapping the schema lacks — type_2d=true maps to CPUParticles2D and false to GPUParticles3D — but says nothing about parent_path's default or whether name is auto-generated.

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 pairs a specific verb ("Add") with concrete resources ("GPUParticles3D or CPUParticles2D node") and a target ("the scene"), so the operation is unmistakable. It stops short of distinguishing itself from siblings like add_node, batch_add_nodes, or apply_particle_preset, which also touch scene nodes.

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 choose this over add_node or batch_add_nodes, no stated prerequisites (e.g., whether a scene must already be open), and no mention of related tools like apply_particle_preset. The agent must infer everything about selection from the tool name.

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