Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_niagara_data_interface_array

DestructiveIdempotent

Set numeric values of a Niagara System user-parameter array data interface by replacing all existing array contents, supporting FloatData and IntData arrays.

Instructions

Set the numeric values of an array user-parameter data interface (e.g. ArrayFloat FloatData / int32 array IntData).

Returns: { system_path: string, parameter_name: string, array_property: string, element_type: string, count: int, values: [number], set: bool, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valuesYesArray of numbers to store (replaces all existing array contents)
system_pathYesAsset path of the Niagara System.
array_propertyNoOptional array UPROPERTY to set (default "FloatData"; e.g. "IntData" for the int32 array DI)
parameter_nameYesShort name of the user-parameter array DI (no "User." prefix)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / required
      Previous value: -[
-  "parameter_name",
-  "values"
-]New value: +[
+  "system_path",
+  "parameter_name",
+  "values"
+]
  2. First observedv1.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true, readOnly=false, so the safety profile is covered. The description goes beyond them by disclosing the exact return shape, including set, saved, and the optional save_error, which tells the agent that the write is persisted and can partially fail on save.

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 tight blocks: a single purpose sentence followed by the return signature. Nothing is wasted and the core verb is front-loaded, though the examples run slightly long for a one-line purpose.

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, but the description supplies the full return shape, which is what would otherwise be missing. Combined with annotations covering the mutation/safety profile and a fully described schema, an agent has what it needs to invoke the tool 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 coverage is 100%, so all four parameters are documented in the schema, giving a baseline of 3. The description's FloatData/IntData examples loosely illustrate the array_property parameter but add no syntax beyond what the schema already provides.

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 (Set) and resource (numeric values of an array user-parameter data interface), and the parenthetical examples (FloatData/IntData) pin down exactly what kind of data interface is meant. This implicitly separates it from the sibling set_niagara_data_interface_curve/_default/_asset tools, though no sibling is named outright.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to choose this over the many sibling data-interface setters (set_niagara_data_interface_default, set_niagara_data_interface_curve, set_niagara_user_parameter, etc.), nor any prerequisite such as requiring the DI to already exist via add_niagara_data_interface. Usage must be inferred entirely from the name.

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