Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_niagara_emitter_handle_info

Read-onlyIdempotent

Read a Niagara System emitter handle by display name or 0-based index to retrieve its ID, enabled/valid flags, version GUID, and local-space or deprecated status.

Instructions

Read one emitter handle of a Niagara System asset, chosen by display name or 0-based index: its id, id name, enabled and valid flags, version GUID and, when it has emitter data, its local-space and deprecated flags. Read-only; list every handle with get_niagara_emitter_handles.

Returns: { system_path: string, emitter_name: string, emitter_id: string, emitter_id_name: string, is_enabled: bool, is_valid: bool, emitter_version: string, is_local_space?: bool, is_deprecated?: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
system_pathYesNiagara System asset path, e.g. "/Game/FX/NS_Fire"; the call fails without it.
emitter_nameNoDisplay name of the handle (case-insensitive); when non-empty it wins over emitter_index.
emitter_indexNo0-based position in the emitter list of the system, used only when emitter_name is absent or empty.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.2.0
    • changedInput schema / properties / emitter_index / description
      Previous value: -"Optional zero-based index; used if emitter_name not provided"New value: +"0-based position in the emitter list of the system, used only when emitter_name is absent or empty."
    • changedInput schema / properties / emitter_name / description
      Previous value: -"Optional display name of the emitter handle"New value: +"Display name of the handle (case-insensitive); when non-empty it wins over emitter_index."
    • changedInput schema / properties / system_path / description
      Previous value: -"Asset path of the Niagara System."New value: +"Niagara System asset path, e.g. \"/Game/FX/NS_Fire\"; the call fails without it."
    • addedInput schema / required
      Added value: +[
+  "system_path"
+]
  2. First observedv1.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds useful behavioral context beyond that: it explains that local-space and deprecated flags are only returned "when it has emitter data" and reinforces that the call is read-only.

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 description is front-loaded with the core action and scope, then provides a compact return-shape block. The Returns block is not waste because no output schema exists, and every sentence contributes useful information.

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?

With no output schema, the description compensates by listing the returned fields and their optionality. Annotations cover the read-only/idempotent safety profile, the input schema fully documents the three parameters, and the sibling routing is explicit, so nothing material 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%, and the schema already documents the precedence of emitter_name over emitter_index and the case-insensitive matching. The description restates that the handle is chosen by display name or 0-based index but adds no format or edge-case detail beyond the schema, so the baseline score of 3 is appropriate.

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 uses a specific verb and resource ("Read one emitter handle of a Niagara System asset") and immediately bounds the scope to a single handle chosen by name or index. It also distinguishes itself from the sibling list operation by naming get_niagara_emitter_handles, so an agent can route 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?

It explicitly says to use get_niagara_emitter_handles to "list every handle," which is a direct alternative for the broader operation. The selection mechanism (display name or 0-based index) is stated, making the when-to-use condition clear.

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