Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

reorder_niagara_modules

Destructive

Move a Niagara module to a new index in an emitter stack to change its execution order. Specify the system, emitter, module name, and target index.

Instructions

Move a UNiagaraNodeFunctionCall module to a new index in its Niagara emitter stack (in-place reordering).

Returns: { system_path: string, emitter_name: string, script_group: string, module_name: string, old_index: int, new_index: int, target_index: int, reordered: bool, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
module_nameYesDisplay name of the module to move
system_pathYesAsset path of the Niagara System.
emitter_nameYesName of the emitter handle.
script_groupNoOptional "spawn" or "update"; defaults to "update"
target_indexYesNon-negative target index in the ordered stack

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false. The description adds useful behavior beyond them: it identifies the operation as an in-place reorder and documents a return payload containing old_index/new_index/reordered/saved/save_error, revealing that the tool persists (saves) the asset and can report save failure. This is meaningful mutation/side-effect context not covered by annotations.

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?

Front-loaded purpose sentence followed by a structured return-shape block. Every part earns its place, and the return detail compensates for the missing output schema. Slightly verbose but well organized.

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 mutation tool with full schema coverage and destructive annotations, the definition covers what the agent needs, including the return fields absent an output schema. It would be fully complete with a note on prerequisites (module must exist in the stack) and any save/permission caveats.

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 description coverage is 100%, so the schema already documents all five parameters (module_name, system_path, emitter_name, script_group with default, target_index). The description adds no additional parameter syntax or constraints beyond what the schema provides, so 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+scope: 'Move a UNiagaraNodeFunctionCall module to a new index in its Niagara emitter stack (in-place reordering).' This clearly distinguishes reordering from sibling mutations like add_niagara_module_to_stack or remove_niagara_module_from_stack, though it does not explicitly name any sibling for differentiation.

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?

The description gives no guidance on when to use this tool versus alternatives, nor prerequisites. It does not mention that the module must already exist in the stack, nor reference any sibling reorder/move tool. Only the bare operation is described.

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