Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

remove_niagara_module_from_stack

Destructive

Remove a function-call module node from a Niagara emitter's spawn or update graph to clean up the stack; the change is saved and verified.

Instructions

Remove a UNiagaraNodeFunctionCall module from a Niagara emitter's spawn or update graph.

Returns: { system_path: string, emitter_name: string, script_group: string, module_name: string, removed: bool, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
module_nameYesDisplay name of the module function-call node to remove
system_pathYesAsset path of the Niagara System.
emitter_nameYesName of the emitter handle.
script_groupNoOptional "spawn" or "update"; defaults to "update"

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond them: the returned 'saved' boolean and optional 'save_error' reveal that the tool persists the asset automatically and can report save failures, which the agent cannot learn from the annotations.

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

Conciseness5/5

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

Two tight sentences: the action is front-loaded, followed by the return shape. Every clause carries information with no filler, and the reader gets purpose and output in the first glance.

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?

No output schema exists, but the description supplies the return shape (removed, saved, save_error), and annotations plus the fully-covered schema cover parameters and safety. It could note failure cases such as a module not being found in the stack, but overall an agent has what it needs to call the tool correctly.

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 all four parameters are already documented in the schema with their formats and defaults. The description adds only the loose phrase 'spawn or update graph' mapping to script_group, so it neither extends nor compensates beyond the schema, placing it at the baseline 3.

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 states a specific verb (Remove), the exact node type (UNiagaraNodeFunctionCall module), and the precise location (a Niagara emitter's spawn or update graph). This distinguishes it cleanly from the add, duplicate, and reorder siblings without opening any schema.

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?

Usage is only implied by the verb 'Remove'. There is no explicit statement of when to prefer this over add_niagara_module_to_stack, add_niagara_module_to_graph, or duplicate_niagara_module_in_stack, nor any prerequisite such as the module needing to already exist in the named graph.

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