Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_gameplay_cue_notify_burst_properties

DestructiveIdempotent

Set GameplayCueTag or IsOverride on a UGameplayCueNotify_Burst Blueprint's CDO and save without recompiling. Requires a registered tag; returns the updated values.

Instructions

Set GameplayCueTag (mirrored into GameplayCueName) and/or IsOverride on the CDO of a UGameplayCueNotify_Burst Blueprint, then save it without recompiling. Needs at least one; an unregistered tag fails before anything is written. Burst effects (particles, sounds) are not authored. Returns the values read back.

Returns: { cue_notify_path: string, properties_set: int, gameplay_cue_tag: string, gameplay_cue_name: string, is_override: bool, note: string, set: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
is_overrideNoOptional bool: this cue overrides parent-tag cues instead of running in addition
cue_notify_pathYesAsset path of the GameplayCueNotify_Burst Blueprint, e.g. "/Game/GAS/Cues/GCN_Hit".
gameplay_cue_tagNoOptional registered GameplayCue tag (sets GameplayCueTag + mirrors GameplayCueName); unregistered -> clean error

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / cue_notify_path / description
      Previous value: -"Full asset path of the GameplayCueNotify_Burst Blueprint"New value: +"Asset path of the GameplayCueNotify_Burst Blueprint, e.g. \"/Game/GAS/Cues/GCN_Hit\"."
  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?

Goes beyond annotations by disclosing that the asset is saved without recompiling, that validation is atomic (fail-fast before any write on an unregistered tag), and that it returns values read back. The idempotent/destructive hints are consistent with this. Adds real behavioral context the annotations alone do not convey.

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-loads the action and constraint sentence, then notes the return shape. Slightly redundant in saying both 'Returns the values read back' and enumerating the return object, but the density is justified and there is little waste.

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?

A mutation tool with no output schema and only four annotations; the description compensates by spelling out validation behavior, the save side effect, scope exclusions, and the return fields. Complete enough for correct invocation, with only minor redundancy.

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 baseline is 3; the description earns an extra point by adding the cross-parameter constraint 'needs at least one' and clarifying that gameplay_cue_tag mirrors into GameplayCueName. Modest but genuine value beyond the per-field schema text.

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+resource+scope: set GameplayCueTag/IsOverride on the CDO of a Burst Blueprint and save. The 'Burst' qualifier implicitly distinguishes it from the sibling actor/looping/static setters, though it never names an alternative. Clear, but no explicit sibling differentiation.

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?

'Needs at least one; an unregistered tag fails before anything is written' and 'Burst effects are not authored' give operating constraints and scope limits. However, there is no when-to-use-vs-alternatives guidance against the three sibling cue-notify setters, so usage is only implied.

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