Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_niagara_module_info

Read-onlyIdempotent

Retrieve details for a Niagara module node in an emitter's spawn or update graph, including script, pins, and enabled state, using system path, emitter, and module name.

Instructions

Read detail for a single UNiagaraNodeFunctionCall module in a Niagara emitter's spawn or update graph.

Returns: { system_path: string, emitter_name: string, script_group: string, module_name: string, node_guid: string, stack_index: int, total_modules_in_stack: int, function_script?: string, function_script_class?: string, is_enabled?: bool, input_pin_count: int, output_pin_count: int, is_deprecated: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
module_nameYesDisplay name of the module function-call node
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 this is a safe, idempotent, read-only, non-open-world operation, so the bar is lower. The description adds that it returns node-instance level state (node_guid, stack_index, is_deprecated, optional function_script), which clarifies it reads a specific stack occurrence rather than a module type.

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?

Purpose is front-loaded in one sentence, followed by the return shape. The return block is somewhat long but earns its place given there is no output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read tool with no output schema, the description compensates by enumerating the return fields, and annotations cover the safety profile. The remaining omission (not-found/error behavior) is minor.

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 including the spawn/update default are documented in the schema. The description adds no parameter-level meaning beyond that baseline.

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?

Specific verb+resource: 'Read detail for a single UNiagaraNodeFunctionCall module,' scoped to an emitter's spawn or update graph. This clearly separates the instance-level read from siblings like get_niagara_module_stack (whole stack) or get_niagara_module_input (pin inputs).

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 scope implies when it applies (inspecting one module node), but there is no explicit when-to-use guidance and no mention of alternatives such as get_niagara_module_stack or get_niagara_module_input. Usage is left to inference.

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