Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_niagara_data_interface_info

Read-onlyIdempotent

Retrieve detailed properties and a UPROPERTY dump for a Niagara System's user-parameter data interface binding by asset path and parameter name.

Instructions

Get detail and a UPROPERTY dump for one UNiagaraDataInterface user-parameter binding on a Niagara system.

Returns: { system_path: string, parameter_name: string, data_interface_class: string, data_interface_class_path: string, path_name: string, properties: [{ name, type }], property_count: int }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
system_pathYesAsset path of the Niagara System.
parameter_nameYesShort name of the user-parameter DI

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), lowering the bar. The description adds real value beyond them by describing the return shape ('UPROPERTY dump', properties array, property_count) in the absence of an output schema.

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?

Two sentences with zero waste: the action and scope come first, followed by the exact return structure. Every clause carries information the agent needs.

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 read tool with no output schema, the description supplies the return shape and annotations supply safety, so an agent has what it needs to call it. The only minor gap is the lack of explicit guidance on when to prefer it over the sibling list tools.

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 both parameters are already documented ('Asset path of the Niagara System', 'Short name of the user-parameter DI'). The description adds no syntax, format, or edge-case detail beyond that, so 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 ('Get') and a precisely scoped resource ('detail and a UPROPERTY dump for one UNiagaraDataInterface user-parameter binding'). The word 'one' implicitly separates it from the sibling list tools like get_niagara_data_interfaces, though no sibling is named explicitly.

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 only implied by the singular scope ('one ... binding'), which suggests this is the single-item lookup versus the plural list tool. There is no explicit when-to-use/when-not statement or named alternative, so an agent must infer the routing.

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