Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

remove_niagara_renderer

Destructive

Removes a Niagara emitter renderer by index, validates the index, recompiles the system, and saves the asset.

Instructions

Remove a renderer from a Niagara emitter by index. Validates that renderer_index is in range, removes from the emitter's RendererProperties array, requests a system compile and saves the asset.

Returns: { system_path: string, emitter_name: string, removed_renderer_index: int, removed_renderer_class: string, renderer_count_after: int, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
system_pathYesAsset path of the Niagara System.
emitter_nameYesName of the emitter handle.
renderer_indexYes0-based index into the emitter's renderers list (use get_niagara_emitter_renderers to find the index)

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.3/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds meaningful side-effect detail beyond them: it validates index range, mutates the emitter's RendererProperties array, requests a system compile, and saves the asset. That compile-and-save chain is exactly the behavioral context an agent needs before invoking a destructive mutation.

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?

The action is front-loaded in the first sentence, followed by a compact side-effect clause and a return-shape block. Since no output schema exists, the explicit return object earns its place rather than being redundant, and there is no filler.

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 destructive mutation tool with no output schema, the description covers the operation, the validation behavior, the persistence side effects (compile + save), and the returned fields. Nothing an agent needs to call it correctly or predict its results is missing.

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 three parameters including the 0-based indexing and the get_niagara_emitter_renderers hint. The description echoes the 'by index' concept but adds no syntax or format detail beyond what the schema provides; 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?

The description states a specific verb and resource ('Remove a renderer from a Niagara emitter') and adds the identifying mechanism ('by index'), which cleanly distinguishes it from add_niagara_renderer, set_niagara_renderer_properties, and get_niagara_renderer_info. An agent can tell what this does 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 implied (remove a renderer from an emitter), but the description never explicitly states when to use this versus the sibling set, nor does it name an alternative. The pointer to get_niagara_emitter_renderers for finding the index lives only in the schema, not the description, so guidance here is inferred rather than stated.

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