Skip to main content
Glama
aadeshrao123

Unreal-MCP

by aadeshrao123

set_niagara_rapid_iteration_parameter

Set rapid iteration parameter values on Niagara modules to control spawn rate, colors, forces, sizes, and lifetimes. First discover available parameters with get_niagara_rapid_iteration_parameters.

Instructions

Set a rapid iteration parameter value on a module.

This is the primary way to change module input values like spawn rate, colors, forces, sizes, lifetimes, etc. Use get_niagara_rapid_iteration_parameters first to discover available parameters and their types.

Value format depends on type: float: 5.0 int: 10 bool: true/false vector: {"x": 1, "y": 2, "z": 3} or [1, 2, 3] color: {"r": 1, "g": 0.5, "b": 0, "a": 1} or [1, 0.5, 0, 1]

Args: system_path: Path to the Niagara System asset emitter_name: Name of the target emitter module_name: Module name (e.g. "SpawnRate", "InitializeParticle", "GravityForce") input_name: Input parameter name (e.g. "SpawnRate", "Color", "Gravity") value: Value to set (type must match the parameter's type) script_usage: Stack the module is in — emitter_update, particle_spawn, particle_update, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYes
input_nameYes
module_nameYes
system_pathYes
emitter_nameYes
script_usageYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, but the description details the operation (setting a value) and explains value formats for different types. It does not mention side effects or permissions, but the behavioral traits are adequately disclosed for a mutation tool.

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?

The description is well-structured with a main statement, usage tip, value format section, and argument list. It is slightly long but each part adds value; minor redundancy could be trimmed.

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?

Given the 6 parameters and no enums, the description covers the tool's purpose, usage, and parameter semantics thoroughly. It lacks details on the output schema, but that is signaled separately, making the description adequately complete.

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

Parameters5/5

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

With 0% schema description coverage, the description compensates fully by explaining all 6 parameters in detail, including value format examples for float, int, bool, vector, and color. This adds significant meaning beyond the bare 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 sets a rapid iteration parameter value on a module, with specific examples like spawn rate, colors. It distinguishes from sibling tools by positioning itself as the primary way to change module inputs and points to get_niagara_rapid_iteration_parameters for discovery.

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 advises to use get_niagara_rapid_iteration_parameters first to discover available parameters, providing clear context. It does not explicitly exclude alternative tools like set_niagara_module_input, but the guidance is sufficient for typical use.

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/aadeshrao123/Unreal-MCP'

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