Skip to main content
Glama

unreal_spawn_niagara_system

Spawns a Niagara system actor in Unreal Engine 5, letting AI clients add particle effects to levels through the UnrealEngineMCP bridge.

Instructions

Spawn a Niagara actor.

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_spawn_niagara_system"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing. It doesn't say this is a mutating operation, whether changes are transient until saved, what permissions or editor state are needed, or what happens on failure.

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

Conciseness3/5

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

It is a single short sentence with no wasted words, but that brevity comes at the cost of under-specification rather than efficient communication. There is no front-loaded context beyond the action itself.

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 needn't be explained, but the opaque single parameter is completely undocumented in both schema and description. For a spawn/mutation tool with no annotations, the definition leaves the agent without enough information to invoke it confidently.

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?

The single parameter is an untyped "params" object with 0% schema description coverage and no nested structure, and the description adds nothing about its expected contents. An agent has no way to know what must be passed in to spawn the system correctly.

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

Purpose3/5

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

The verb+resource ("Spawn a Niagara actor") is specific enough to convey that this creates a Niagara actor instance rather than a Niagara system asset, but it never distinguishes itself from close siblings like unreal_create_niagara_system or unreal_spawn_actor. An agent must infer from names alone whether this instantiates an existing system or creates a new one.

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

Usage Guidelines2/5

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

There is no guidance on when to use this instead of unreal_create_niagara_system or unreal_spawn_actor, and no prerequisites (level context, whether the system asset must already exist, whether saving afterward with unreal_save_niagara_system is required). Only the bare action is implied.

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