Skip to main content
Glama

unreal_set_niagara_parameter

Sets a Niagara user parameter so you can control particle behavior in Unreal Engine 5 effects from an AI client.

Instructions

Set a Niagara user parameter.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full disclosure burden, and it discloses nothing: it does not say whether the change is transient or persisted (there is a sibling unreal_save_niagara_system), what permissions or asset state are required, or what happens on an invalid parameter name. For a mutation tool with zero annotation coverage this is a severe gap.

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 single sentence is trivially short, but this is under-specification rather than conciseness; every useful detail (target object, parameter identification, value form) is absent. There is nothing to trim, yet the sentence does not earn its place as a definition.

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?

An output schema exists, so return values need not be explained, but for a mutation tool with an undocumented free-form 'params' object the description should at minimum describe the expected argument shape and the target asset. As written an agent cannot construct a correct call from the definition alone.

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

Parameters1/5

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

Schema description coverage is 0% and the single parameter 'params' is declared with no type, title detail, or sub-properties, so the schema conveys almost nothing. The description does not compensate at all — it never mentions that a system/component reference, a parameter name, and a value must be supplied, leaving the only required argument completely opaque.

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

Purpose2/5

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

The description is essentially a restatement of the tool name: 'Set a Niagara user parameter' adds only the qualifier 'user' beyond the identifier unreal_set_niagara_parameter. It does not identify what a user parameter is, where it lives, or which Niagara object is targeted, so an agent cannot distinguish it meaningfully from siblings like unreal_set_material_parameter or unreal_get_niagara_parameters.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as reading parameters first with unreal_get_niagara_parameters or creating a system with unreal_create_niagara_system. The agent must infer usage entirely 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