Skip to main content
Glama
aadeshrao123

Unreal-MCP

by aadeshrao123
OverviewSchemaRelated ServersScoreDiscussions
Local

add_niagara_user_parameter

Add a typed user parameter to a Niagara System, supporting primitives, structs, enums, and data interfaces.

Instructions

Add a user parameter to a Niagara System. Supports every type the editor's User Parameters "+" menu can add — primitives, structs, enums, and Data Interfaces.

Use list_niagara_parameter_types to discover valid type names before calling.

Args: system_path: Path to the Niagara System asset parameter_name: Name for the new parameter (auto-prefixed with "User.") parameter_type: Type name. Resolved via NiagaraTypeRegistry, so anything Niagara registered is valid. Examples: - Primitives: "float", "int", "bool", "Vector2", "Vector", "Vector4", "LinearColor", "Quat", "Position", "Matrix" - Niagara structs: "NiagaraID", "NiagaraRandInfo", "NiagaraSpawnInfo" - Enums: "ENiagaraExecutionState", any registered UEnum path - Data Interfaces (bare or prefixed): "ArrayFloat", "ArrayVector", "ArrayVector4", "ArrayInt32", "Curve", "Vector2DCurve", "VectorCurve", "Vector4Curve", "CurlNoise", "Grid2D", "Grid3D", "SkeletalMesh", "StaticMesh", "Texture", "TextureCube", "VolumeTexture", "Texture2DArray", "RenderTarget2D", "SplineComponent", "Camera", "Collision", "PhysicsAsset", "Spline", and any other NiagaraDataInterface subclass including plugin-provided ones. default_value: Optional default. For scalars pass as string or number; for vector/color/struct pass UE-standard text form like "(X=1,Y=2,Z=3)" or "(R=1,G=0.5,B=0,A=1)". Data interfaces use the CDO defaults — use set_niagara_user_parameter afterwards for richer initialization.

Returns the created parameter with its resolved type name, kind (primitive / struct / enum / data_interface / object), size_bytes, and (for DIs) class_path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
system_pathYes
default_valueNo
parameter_nameYes
parameter_typeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

With no annotations, description fully discloses behavior: auto-prefixing parameter name, default value formats, CDO defaults for data interfaces, and return value structure. No contradictions.

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?

Well-structured with clear sections, examples, and return description. Slightly lengthy but every sentence adds value. Front-loaded with key purpose and type support mention.

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?

Given complexity (many type names, optional default) and presence of output schema, description covers purpose, parameters, types, usage guidance, and return. References sibling tool for further initialization, making it complete.

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

Parameters5/5

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

Schema has 0% coverage, but description adds extensive meaning for all parameters: system_path, parameter_name (prefix), parameter_type (with long examples), and default_value (with format details). Compensates fully.

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?

Description clearly states 'Add a user parameter to a Niagara System' and specifies the scope of supported types. It distinguishes from sibling tools like set_niagara_user_parameter and remove_niagara_user_parameter.

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

Usage Guidelines4/5

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

Provides explicit guidance to use list_niagara_parameter_types to discover valid type names. Includes detailed examples and references to set_niagara_user_parameter for richer initialization. Lacks explicit 'when not to use' but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aadeshrao123/Unreal-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server