Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_niagara_emitter_requires_persistent_ids

DestructiveIdempotent

Toggle bRequiresPersistentIDs on a Niagara emitter to keep Particles.ID stable across frames, with a small performance cost.

Instructions

Toggle bRequiresPersistentIDs on a Niagara emitter (stable Particles.ID across frames; small perf cost).

Returns: { system_path: string, emitter_name: string, requires_persistent_ids: bool, applied: bool, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
system_pathYesAsset path of the Niagara System.
emitter_nameYesName of the emitter handle.
requires_persistent_idsNoBoolean to assign

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / required
      Previous value: -[
-  "emitter_name"
-]New value: +[
+  "system_path",
+  "emitter_name"
+]
  2. First observedv1.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly=false, destructive=true, idempotent=true), and the description adds real context: the small performance cost of enabling persistent IDs and the return shape showing applied/saved/save_error, which discloses that the emitter asset is saved and that saving can fail. This goes meaningfully beyond the structured hints.

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?

Two compact sentences; the core action and its semantic consequence are front-loaded and the return shape is clearly separated. No filler, though the 'Toggle' wording is a small wasted ambiguity.

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?

For a 3-parameter mutation with no output schema, the description supplies the return field list and the key performance caveat, which is enough for an agent to call it correctly. It does not resolve the toggle-vs-set wording, a minor gap.

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 all three parameters are already documented. The parenthetical explains the semantic effect of the boolean but adds no per-parameter format or default detail, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb, resource, and property ('Toggle bRequiresPersistentIDs on a Niagara emitter'), which distinguishes it from the many sibling set_niagara_emitter_* tools. The only imprecision is the word 'Toggle' when the schema actually takes an explicit boolean, so it is closer to a set than a flip.

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 parenthetical ('stable Particles.ID across frames; small perf cost') gives the agent an implied reason to use it and signals the tradeoff, but there is no explicit when-to-use, when-not, or sibling alternative. Usage is inferable rather than stated.

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