Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_niagara_decal_renderer

Add decal renderer properties to a Niagara emitter with material, source mode, visibility, and screen-size fade, then compile and save the system.

Instructions

Add a NiagaraDecalRendererProperties (UNiagaraDecalRendererProperties) to a Niagara emitter with decal-specific defaults applied via reflection. Companion to add_niagara_renderer with renderer_type='Decal' — use this cmd when you want to seed decal config (material, source mode, visibility tag, screen-size fade) in the same call. Then requests a system compile and saves.

Returns: { system_path, emitter_name, renderer_index, renderer_class, material_path, source_mode, renderer_visibility, decal_screen_size_fade, renderer_count, save_error? }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_modeNoOptional ENiagaraRendererSourceDataMode name (Particles/Emitter). Default Particles.
system_pathYesAsset path of the Niagara System (e.g. "/Game/Niagara/NS_Example").
emitter_nameYesName of the emitter handle (the human-readable name in the system's emitter list).
material_pathNoOptional asset path; sets the renderer's Material UPROPERTY.
renderer_visibilityNoOptional int32 visibility tag (default 0).
decal_screen_size_fadeNoOptional float fade threshold (default 0.0).

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

A4.3/5.0
Behavior4/5

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

Annotations mark it as a non-read-only, non-idempotent write, and the description adds genuinely useful behavior beyond that: defaults are applied via reflection, a system compile is requested, and the system is saved. It also surfaces a save_error field. It stops short of saying what happens on an invalid system_path or duplicate renderer, so it is not fully exhaustive.

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-loads the action in the first sentence, then the routing guidance, then the persistence side effect. The appended Returns block is slightly dense but earns its place by documenting the return shape in the absence of an output schema. Little wasted text.

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?

With no output schema, the description compensates by listing the return fields, and annotations plus a fully-described schema cover safety and arguments. Remaining gaps are edge-case behavior (missing emitter, invalid material path, duplicate renderer) rather than anything needed to invoke it 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 the schema already documents all six parameters including the optional ones and their defaults. The description only echoes which fields get seeded (material, source mode, visibility tag, screen-size fade) without adding syntax, valid ranges, or format beyond the schema, so the baseline 3 applies.

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 (add a NiagaraDecalRendererProperties to a Niagara emitter) with the concrete class name. It also explicitly distinguishes itself from the sibling add_niagara_renderer by explaining the Decal renderer_type path and when this variant is preferable.

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?

Gives an explicit when-to-use rule: pick this cmd over add_niagara_renderer with renderer_type='Decal' when you want to seed decal config (material, source mode, visibility tag, screen-size fade) in a single call. The alternative and the selecting condition are both named.

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