Skip to main content
Glama
Dex865378

Godot MCP Server Ultimate Edition

by Dex865378

create_particles

Creates a GPUParticles3D node with a preset (smoke, fire, snow, rain, sparks, dust) to add particle effects to a Godot scene.

Instructions

Create a GPUParticles3D node with a preset configuration (smoke, fire, snow, rain, sparks, dust).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYesPath to the Godot project directory
scenePathYesScene file path
parentPathNoParent node path (default: root)
presetNoParticle preset: "smoke", "fire", "snow", "rain", "sparks", "dust"
optionsNoOptions: { amount: int, lifetime: float, gravity: [x,y,z], color: [r,g,b,a], position: [x,y,z] }
Behavior2/5

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

No annotations provided, so description must fully disclose behavior. It only states creation with preset, but omits side effects (e.g., node insertion, overwrite behavior) or requirements (scene open).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence with no wasted words, effectively communicates the core function.

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?

Despite schema coverage, the description lacks information on default behaviors, return values, and scenario applicability. For a 5-parameter tool with nested objects, this is insufficient for full agent understanding.

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% with descriptions for all parameters. The description adds marginal value by specifying the node type and listing presets, but these are already in the schema. Options parameter details are not expanded.

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

Purpose5/5

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

Description clearly states it creates a GPUParticles3D node with preset configurations, listing common presets. This distinguishes it from generic node creation tools like 'add_node'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for creating particle effects but provides no explicit guidance on when to use this over alternative node creation tools, nor any exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Dex865378/Dex865378-MCP-GODOT-63-HERRAMIENTAS'

If you have feedback or need assistance with the MCP directory API, please join our Discord server