Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

edit_anim_notify

Destructive

Edit an existing animation notify event on a UAnimSequence by notify name and occurrence, updating fields in an undo transaction and saving the sequence.

Instructions

Edit an existing FAnimNotifyEvent on a UAnimSequence (identified by name + occurrence) in an undo transaction and save it. No editable field is an error before anything changes; edits that leave the event as it is are a success with applied=false, applied_count 0 and saved=false, and the sequence is neither modified nor saved. A failed save makes success false, with saved=false and save_error.

Returns: { animation_path, notify_name, occurrence_index, matched_count, notify, applied_count, applied, saved, save_error, message }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeNoNew trigger time in seconds (FAnimNotifyEvent::SetTime). Optional.
durationNoNew duration in seconds (FAnimNotifyEvent::SetDuration; meaningful for notify-state). Optional.
notify_nameYesNotifyName of the event to edit (FName). Names are not unique; see occurrence_index.
track_indexNoNew TrackIndex (zero-based). Optional.
animation_pathYesFull asset path to the UAnimSequence.
trigger_chanceNoNew NotifyTriggerChance in [0,1]. Optional.
occurrence_indexNoZero-based index AMONG events sharing notify_name (default 0)
montage_tick_typeNoNew MontageTickType: 'Queued' or 'BranchingPoint'. Optional.
trigger_weight_thresholdNoNew TriggerWeightThreshold. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations (destructiveHint=true, idempotentHint=false) by disclosing the undo-transaction/save model, that an empty edit set errors before any mutation, that a no-op edit reports applied=false/applied_count 0/saved=false with the sequence untouched, and that a failed save yields success=false plus save_error. This is exactly the extra context annotations cannot carry.

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?

Opens with the action, then the no-op and failure semantics, then the return shape — well front-loaded and free of filler. Slightly dense but every clause carries distinct information.

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 destructive mutation with no output schema, the description supplies the outcome contract (success/applied/applied_count/saved/save_error) and the no-op and failure paths, so an agent can act and interpret results without further documents.

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 each of the 9 parameters carries its own UE-level explanation, so the schema does the heavy lifting. The description only reinforces the notify_name + occurrence_index pairing, which is already documented in the schema, so the 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 ('Edit') and resource ('an existing FAnimNotifyEvent on a UAnimSequence') and pins down identity semantics (name + occurrence). The word 'existing' cleanly separates it from add_anim_notify/add_montage_notify and remove_anim_notify without needing to name them.

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?

Makes clear this operates on an already-present event and requires at least one editable field, implied preconditions for when to reach for it. It does not explicitly name an alternative tool or state exclusions, so it stops short of a 5.

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