Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_niagara_emitter_sim_target

Read-onlyIdempotent

Fetch a Niagara emitter's simulation target, local-space, and deterministic settings using its system path and emitter name.

Instructions

Get the simulation target configuration of a Niagara emitter. Reads SimTarget, bLocalSpace and bDeterministic from the emitter's FVersionedNiagaraEmitterData.

Returns: { system_path: string, emitter_name: string, sim_target: string, is_local_space: bool, is_deterministic: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
system_pathYesAsset path of the Niagara System (e.g. "/Game/Niagara/NS_Example").
emitter_nameYesDisplay name 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.7/5.0
Behavior4/5

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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive, not open-world), so the bar is low. The description adds real context beyond them by naming the underlying data source (FVersionedNiagaraEmitterData) and spelling out the return object, sparing the agent a guess about output shape.

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?

Two short, front-loaded sentences: purpose first, then the explicit return contract. No filler or redundant restatement of the name, though the return block is somewhat terse.

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?

For a simple, parameter-light, read-only getter, this is complete: it says what is read, from where, and what comes back. With no output schema present, the inline return description is exactly the missing piece an agent needs, and the annotations cover the rest.

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 both required parameters (system_path, emitter_name) are documented with examples in the schema itself. The description adds no parameter-level meaning 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get the simulation target configuration of a Niagara emitter') and enumerates exactly which fields are read (SimTarget, bLocalSpace, bDeterministic), so scope is unambiguous. It does not explicitly distinguish itself from nearby read siblings like get_niagara_emitter_handle_info, but the narrowed field list effectively does that work.

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 by the tool name and the read-only nature of the operation, but the description never says when to reach for this versus alternatives such as get_niagara_emitter_handle_info or get_niagara_emitter_runtime_summary. No exclusions or prerequisites are 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