Skip to main content
Glama

particles

Idempotent

Create and configure Godot particle systems: add GPU particle nodes (2D/3D), set emission/process parameters, load presets, and apply materials. Works at runtime for the current context.

Instructions

创建 GPUParticles2D/3D 节点、设置发射/处理参数、加载预设效果、设置粒子材质。运行时操作,仅影响当前执行上下文。如需持久化,请编辑 .tscn 文件。运行时操作,仅影响当前执行上下文。如需持久化,请编辑 .tscn 文件。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo节点名称(particles_create)
actionYes操作类型
amountNo发射数量(正整数)
parentNo父节点路径(默认 root)
presetNo预设效果名称
spreadNo扩散角度(0-180 度)
dampingNo阻尼
gravityNo重力 {x,y,z}
lifetimeNo粒子生命周期(秒)
positionNo位置。3D 用 {x,y,z},2D 用 {x,y}
directionNo发射方向 {x,y,z}
node_pathNo粒子节点路径
node_typeNo粒子节点类型(particles_create)
randomnessNo随机性(0-1)
speed_scaleNo速度缩放
project_pathNoGodot 项目目录路径(可选,默认使用 GODOT_PROJECT_PATH 环境变量或当前目录)
explosivenessNo爆发性(0-1)
material_typeNo材质类型(ParticleProcessMaterial)
emission_shapeNo发射形状
load_autoloadsNo是否加载 Autoload 上下文(默认 true)
emission_box_extentsNo盒体发射范围 {x,y,z}(emission_shape=box 时有效)
emission_sphere_radiusNo球体发射半径(emission_shape=sphere 时有效)
Behavior4/5

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

Annotations indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds the crucial behavioral trait that operations are runtime-only and non-persistent, which is not fully captured by the annotations. It doesn't contradict annotations; it reinforces the non-destructive, session-scoped nature.

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

Conciseness2/5

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

The second sentence is a verbatim repeat of the first: '运行时操作,仅影响当前执行上下文。如需持久化,请编辑 .tscn 文件。' This duplication is unnecessary and wastes space. While the description is short, the redundancy means not every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having 22 parameters and five action types, the schema provides thorough parameter documentation, and the description adds high-level runtime/persistence context. It lacks a mention of return values or prerequisites, but given the schema's richness, the description is sufficiently complete for a well-structured tool.

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's generic phrases like '设置发射/处理参数' add no additional meaning beyond the schema's detailed descriptions, which already document parameter relationships (e.g., emission_box_extents only for box shape).

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?

The description explicitly states multiple specific actions: creating GPUParticles2D/3D nodes, setting emission/process parameters, loading presets, and setting materials. This clearly identifies the resource domain and distinguishes the tool from broader scene or material manipulation tools.

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

Usage Guidelines4/5

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

The description says '运行时操作,仅影响当前执行上下文' (runtime operation, only affects current execution context) and directs users to edit .tscn files for persistence. This provides clear guidance on when to use the tool vs. persistent scene edits, though it doesn't explicitly name an alternative particle-specific tool.

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/wgt19861219/godot-mcp-enhanced'

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