Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_niagara_emitter_renderers

Read-onlyIdempotent

List all renderers on a Niagara emitter, including authored properties and mesh slots, to inspect and round-trip renderer settings.

Instructions

List all renderers on a Niagara emitter (read-only). Each entry also dumps the authored renderer UPROPERTYs (base bIsEnabled/SortOrderHint/MotionVectorSetting/bAllowInCullProxies plus the Sprite/Mesh-specific fields present on the concrete class) and, for Mesh renderers, the assigned static-mesh slots — so set_niagara_renderer_properties / set_niagara_mesh_renderer_mesh round-trip.

Returns: { system_path: string, emitter_name: string, renderer_count: int, renderers: [{ index, class, display_name, material_path, properties:{...}, meshes?:[{ slot, mesh_path }] }] }

Input Schema

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

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.9/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 value beyond that: it enumerates exactly which UPROPERTYs get dumped (bIsEnabled, SortOrderHint, MotionVectorSetting, bAllowInCullProxies plus class-specific Sprite/Mesh fields) and that Mesh renderers include static-mesh slots.

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?

It is dense but front-loaded with purpose, then the most useful detail (what each entry dumps), then a compact Returns block. Every clause earns its place; the only mild cost is the long compound middle sentence.

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?

There is no output schema, so the inline Returns shape (system_path, emitter_name, renderer_count, renderers[] with index/class/display_name/material_path/properties/meshes) is valuable and largely closes the gap. Combined with rich annotations, an agent has nearly everything needed to call and interpret the tool.

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% (both system_path and emitter_name documented in-schema), so the schema already carries parameter meaning. The description adds no syntax or format detail beyond what the schema provides, making the baseline 3 correct.

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 opens with a specific verb+resource+scope: 'List all renderers on a Niagara emitter.' An agent can distinguish this collection-listing tool from the singular 'get_niagara_renderer_info' sibling and infer exactly what it returns without opening the 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?

It notes '(read-only)' and explicitly names the write tools it round-trips with, set_niagara_renderer_properties and set_niagara_mesh_renderer_mesh, which implies usage context. However, it never states an explicit when-to-use vs when-not condition, nor how it differs from the closely named sibling get_niagara_renderer_info.

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