Skip to main content
Glama

set_niagara_system_properties

DestructiveIdempotent

Set render and system flags on a Niagara System asset via raw reflection, applying only supplied fields and override companions, then saving and verifying changes without recompiles.

Instructions

Set render/system flags on a UNiagaraSystem asset via raw reflection (no PostEditChangeProperty -> avoids the compile/scalability pipeline). Only the supplied fields are applied; each render override value also sets its bOverride* companion so it actually takes effect on spawned components. Persists via SavePackage and is reopen-clean (no recompile). Idempotent.

Returns: { system_path, applied_count, override_applied:[...], , fixed_bounds:{min,max}, saved, save_error? }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cast_shadowNoOptional bool: default CastShadow for spawned components (sets bCastShadow + bOverrideCastShadow).
system_pathYesAsset path of the Niagara System (e.g. "/Game/Niagara/NS_Example").
fixed_boundsNoOptional object {min:[x,y,z], max:[x,y,z]}: the system FixedBounds FBox. Partial corners keep the current value.
b_fixed_boundsNoOptional bool: bFixedBounds (enables the system FixedBounds box).
receives_decalsNoOptional bool: default ReceivesDecals (sets bReceivesDecals + bOverrideReceivesDecals).
render_custom_depthNoOptional bool: default RenderCustomDepth (sets bRenderCustomDepth + bOverrideRenderCustomDepth).
override_cast_shadowNoOptional bool: explicitly set bOverrideCastShadow (auto-set when cast_shadow is given).
override_receives_decalsNoOptional bool: explicitly set bOverrideReceivesDecals.
custom_depth_stencil_valueNoOptional int: default CustomDepthStencilValue (sets CustomDepthStencilValue + bOverrideCustomDepthStencilValue).
require_current_frame_dataNoOptional bool: bRequireCurrentFrameData.
translucency_sort_priorityNoOptional int: default TranslucencySortPriority (sets it + bOverrideTranslucencySortPriority).
override_render_custom_depthNoOptional bool: explicitly set bOverrideRenderCustomDepth.
support_large_world_coordinatesNoOptional bool: bSupportLargeWorldCoordinates.
translucency_sort_distance_offsetNoOptional float: default TranslucencySortDistanceOffset (sets it + bOverrideTranslucencySortDistanceOffset).
override_custom_depth_stencil_valueNoOptional bool: explicitly set bOverrideCustomDepthStencilValue.
override_translucency_sort_priorityNoOptional bool: explicitly set bOverrideTranslucencySortPriority.
override_translucency_sort_distance_offsetNoOptional bool: explicitly set bOverrideTranslucencySortDistanceOffset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • addedInput schema / required
      Added value: +[
      +  "system_path"
      +]
  2. First observedv1.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Adds rich behavior beyond annotations: raw reflection path avoiding PostEditChangeProperty, automatic bOverride* companion setting so overrides actually take effect, SavePackage persistence, reopen-clean (no recompile), and idempotency. The destructiveHint=true annotation is reconciled by the 'only supplied fields are applied' statement.

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?

Dense but front-loaded: the mechanism and the bOverride behavior come first, then persistence/idempotency, then the return shape. Every sentence carries information; slightly heavy prose prevents a 5.

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?

For a 17-parameter mutation tool with no output schema, the description covers the write semantics, side effects (companion overrides, SavePackage), persistence guarantees, and spells out the return shape inline, so an agent has everything needed to invoke and interpret it.

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 the schema itself already documents each flag including the bOverride companion pairing. The description's aggregate note about auto-setting bOverride* companions is useful but largely restates what the schema already conveys, so baseline 3 applies.

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 specific verb (Set) and resource (render/system flags on a UNiagaraSystem asset) and explains the mechanism (raw reflection). Clearly distinguishable from siblings like set_niagara_system_fixed_bounds, get_niagara_system_properties, and set_niagara_renderer_properties.

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?

Implies usage via the mechanism explanation (avoids compile/scalability pipeline, so prefer when you don't want a recompile) and the 'only supplied fields are applied' constraint, but never states explicitly when to pick this over the sibling set_niagara_system_fixed_bounds, which overlaps with its fixed_bounds parameter.

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