Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_niagara_data_interface_curve

DestructiveIdempotent

Replace all keys of an FRichCurve property on a Niagara data interface curve, rebuilding its lookup table, recompiling, and saving the system within an undo transaction.

Instructions

Replaces all keys of one FRichCurve property on a curve user-parameter data interface of a Niagara system with the given time/value keys (an empty array clears it), rebuilds the DI's lookup table, requests a recompile and saves the system, inside an undo transaction that records the DI; success requires the save. The DI must already exist (add_niagara_data_interface) and curve_property must name an FRichCurve on it: Curve by default, XCurve/YCurve/ZCurve (WCurve too on Vector4) on vector curve DIs, RedCurve/GreenCurve/BlueCurve/AlphaCurve on color curve DIs. For array DIs use set_niagara_data_interface_array.

Returns: { system_path: string, parameter_name: string, curve_property: string, key_count: int, keys: [{time,value}], set: bool, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keysYesArray of { time: number, value: number } keys to set (replaces all existing keys on the channel)
system_pathYesAsset path of the Niagara System.
curve_propertyNoOptional FRichCurve UPROPERTY to author (default "Curve"; e.g. "RedCurve"/"XCurve" on Color/Vector curve DIs)
parameter_nameYesShort name of the user-parameter curve 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",
-  "keys"
-]New value: +[
+  "system_path",
+  "parameter_name",
+  "keys"
+]
  2. First observedv1.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly false, destructive true, idempotent true), but the description goes far beyond: it discloses that all keys are replaced, that an empty array clears the channel, that the lookup table is rebuilt, a recompile is requested, the system is saved, the operation runs inside an undo transaction, and that success requires the save. This is exactly the mutation context an agent needs.

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-loaded with the action and information-dense with no filler; every clause carries a distinct fact. It is long and packed into few sentences, but nothing is redundant, so only a minor deduction for density over compactness.

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 supplies a Returns block (system_path, parameter_name, curve_property, key_count, keys, set, saved, optional save_error), and it covers prerequisites, alternatives, save-required success semantics, and undo behavior. Nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds real meaning beyond the schema by enumerating valid curve_property values (Curve default; XCurve/YCurve/ZCurve and WCurve on Vector4; RedCurve/GreenCurve/BlueCurve/AlphaCurve on color DIs) and noting the empty-array clear semantics. It stops short of adding syntax detail for the time/value key format itself.

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 precise verb and resource: replace all keys of one FRichCurve property on a curve user-parameter data interface of a Niagara system. It explicitly distinguishes itself from the array-DI sibling (set_niagara_data_interface_array), so an agent can route without opening schemas.

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?

Names the prerequisite ('The DI must already exist (add_niagara_data_interface)'), the alternative for the other DI shape ('For array DIs use set_niagara_data_interface_array'), and explains how curve_property maps to DI type. When-to-use and when-to-use-something-else are both explicit.

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