Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

update_transition

Destructive

Update selected metadata fields on a StateTree transition while preserving omitted values and rejecting invalid enum inputs—use for fields not exposed by set_transition_properties.

Instructions

Update any subset of a transition's metadata fields on a state. Only fields explicitly passed are written; everything else is preserved. Unknown enum strings are rejected (no silent no-ops on bad input). Superset of set_transition_properties: adds transition_type (None|Succeeded|Failed|GotoState|Parent|NextState|...), target_state (rebind by name), event_tag (FGameplayTag, when trigger=OnEvent), and payload_struct (event-payload struct, when trigger=OnEvent). Use this when set_transition_properties doesn't expose the field you need.

Returns: { tree_path, state_name, transition_index, applied_fields: [string], errors: [string], saved }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
delayNoOptional bool (when true, delay_duration and delay_variance are honored by the editor)
enabledNoOptional bool (defaults preserved when omitted)
triggerNoOptional EStateTreeTransitionTrigger name (None|OnStateCompleted|OnStateTick|OnEvent|OnDelta|...)
priorityNoOptional EStateTreeTransitionPriority name (Lowest|Low|Normal|High|Highest)
to_stateNoAlias of `target_state` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `target_state`.
event_tagNoOptional event tag as a literal FGameplayTag string (e.g. "GameplayCue.Movement.Jumped")
tree_pathYesAsset path of the UStateTree
state_nameYesState that owns the transition
target_stateNoOptional re-target by state name (only when you want to redirect the edge)
delay_durationNoOptional number (seconds)
delay_varianceNoOptional number (seconds of random variance)
payload_structNoOptional UScriptStruct name or /Script path for the event payload
transition_typeNoOptional EStateTreeTransitionType name (None|Succeeded|Failed|GotoState|Parent|NextState|NextSelectableState|NextParent|NextSelectableParent)
transition_indexNoIndex into the state's Transitions array (0-based)

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.7/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, but the description adds meaningful context beyond them: only explicitly passed fields are written, everything else is preserved, and unknown enum strings are rejected. It also documents the return shape, though it does not discuss permissions or reversibility.

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?

The description is front-loaded with the purpose, followed by mutation semantics, the sibling comparison, and a compact Returns line. Every sentence contributes useful information and there is no filler.

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 14-parameter mutation tool with no output schema and a closely related sibling, the description covers purpose, usage routing, partial-update behavior, validation behavior, and the return shape. Nothing critical for correct invocation is missing.

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 the baseline is 3, but the description adds semantic relationships not spelled out in the schema — notably that event_tag and payload_struct apply when trigger=OnEvent, and that target_state rebinds by name. Those additions give it an edge over the schema alone.

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?

The description gives a specific verb+resource: 'Update any subset of a transition's metadata fields on a state.' It explicitly identifies itself as a superset of set_transition_properties and names the additional fields, so an agent can distinguish it from its sibling without opening the schema.

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

Usage Guidelines5/5

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

It states exactly when to use this tool: 'Use this when set_transition_properties doesn't expose the field you need.' It also explains the superset relationship and lists the extra fields, which is a clear selector between the two tools.

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