Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_niagara_renderer_info

Read-onlyIdempotent

Dump the full UPROPERTY surface of one Niagara renderer: resolves system path, emitter name, and renderer index, then returns its class and a flat JSON property map.

Instructions

Dump the full property set of a specific renderer instance owned by a system emitter. Resolves the system via path, the emitter via name (or handle_index), and the renderer via index — then runs FJsonObjectConverter::UStructToJsonObject on the renderer to produce a flat property map. get_niagara_emitter_renderers lists every renderer; this cmd returns the full UPROPERTY surface of one renderer.

Returns: { system_path, emitter_name, renderer_index, renderer_class, renderer_class_path, properties: {...} }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
system_pathYesContent path to the UNiagaraSystem asset.
emitter_nameYesName of the emitter handle (preferred) or its FName.
handle_indexNoOptional fallback when multiple emitters share a name (0-based).
renderer_indexYes0-based index into FVersionedNiagaraEmitterData::RendererProperties.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral detail beyond that: the three-step resolution chain (path -> emitter name or handle_index -> renderer index) and the fact that output is produced by UStructToJsonObject as a flat property map, which sets expectations about the shape and completeness of the result.

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 with the action and scope, then the resolution mechanics, then the return shape. Every sentence carries information, though the FJsonObjectConverter::UStructToJsonObject implementation reference is slightly more internal detail than an agent strictly needs.

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?

There is no output schema, but the description enumerates the returned fields (system_path, emitter_name, renderer_index, renderer_class, renderer_class_path, properties). Combined with the read-only annotations, nothing an agent needs to call or interpret this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds the semantic relationship among the parameters by describing the resolution order and noting handle_index as a fallback for duplicate emitter names. That relational context is value beyond the per-field schema text, though it does not add new formats or constraints.

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?

States a specific verb and resource ('Dump the full property set of a specific renderer instance') and pins the scope precisely. It explicitly distinguishes itself from the sibling get_niagara_emitter_renderers (which lists all renderers), so an agent can route between them without opening either schema.

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

Usage Guidelines5/5

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

Names the alternative tool and the condition that selects it: 'get_niagara_emitter_renderers lists every renderer; this cmd returns the full UPROPERTY surface of one renderer.' The choice between enumeration and single-renderer inspection is left to nothing.

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