Skip to main content
Glama

particle_system

Create, configure, and control particle systems in Unity: manage modules, playback, color, size, and velocity over lifetime.

Instructions

Manage Unity ParticleSystems in detail. Actions:

  • create: Create a new ParticleSystem GameObject

  • get_info: Get full particle system state (main, emission, shape modules)

  • set_main: Configure main module (duration, looping, lifetime, speed, size, gravity, etc.)

  • set_emission: Configure emission (rate over time/distance)

  • set_shape: Configure shape module (type, radius, angle, arc)

  • set_renderer: Configure renderer (render mode, material, sorting order)

  • play/stop/pause/restart: Playback control

  • list: List all ParticleSystems in scene

  • set_color_over_lifetime: Set start/end color gradient

  • set_size_over_lifetime: Set start/end size curve

  • set_velocity_over_lifetime: Set velocity min/max per axis

  • get_modules: Check which modules are enabled

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoPosition X
yNoPosition Y
zNoPosition Z
arcNoShape arc
nameNoName for new particle system (create)
xMaxNoVelocity X max
xMinNoVelocity X min
yMaxNoVelocity Y max
yMinNoVelocity Y min
zMaxNoVelocity Z max
zMinNoVelocity Z min
angleNoCone angle
actionYesParticleSystem action to perform
radiusNoShape radius
enabledNoEnable/disable module (true/false)
endSizeNoEnd size for size-over-lifetime curve
loopingNoEnable looping (true/false)
durationNoDuration in seconds
endColorNoEnd color JSON: {"r":0,"g":0,"b":1,"a":0}
objectIdNoInstance ID of the ParticleSystem
shapeTypeNoShape type (Sphere, Hemisphere, Cone, Box, Circle, etc.)
startSizeNoStart size
objectPathNoHierarchy path of the ParticleSystem
parentPathNoParent path (create)
renderModeNoBillboard, Stretch, HorizontalBillboard, VerticalBillboard, Mesh
startColorNoStart color JSON: {"r":1,"g":0,"b":0,"a":1}
startSpeedNoStart speed
playOnAwakeNoPlay on awake (true/false)
startSizeOLNoStart size for size-over-lifetime curve
materialPathNoPath to material asset
maxParticlesNoMaximum particles
rateOverTimeNoEmission rate over time
sortingOrderNoSorting order
startLifetimeNoStart lifetime in seconds
gravityModifierNoGravity modifier
simulationSpaceNolocal, world, or custom
rateOverDistanceNoEmission rate over distance
Behavior3/5

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

Annotations only indicate readOnlyHint=false, so description carries burden. It enumerates actions (create, set, play, etc.) that imply modification, but does not disclose side effects, authorization needs, or other behavioral traits beyond the action names.

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?

Bullet-pointed list of actions is well-structured and front-loaded with purpose. Some redundancy (e.g., 'Configure' repeated), but overall efficient and easy to scan.

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

Completeness5/5

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

Given 37 parameters and no output schema, description covers all actions and modules. Agent can infer which parameters apply to which action from context, making it complete for invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, baseline 3. Description adds value by grouping actions and including example JSON for color parameters, which helps interpret the input schema.

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 clearly states it manages Unity ParticleSystems in detail, listing specific actions. It distinguishes from siblings which cover other aspects of Unity (animation, lighting, etc.).

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 lists all possible actions but does not provide explicit when-to-use or when-not-to-use guidance. It implies usage for particle system management, but lacks comparisons to alternatives or exclusions.

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/joel-wehr/unity-mcp'

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