Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_transition_properties

DestructiveIdempotent

Configure trigger, priority, delay, and enabled status for a transition of a state in a UStateTree. Provide the tree path and state name to apply and save changes.

Instructions

Set properties (trigger, priority, delay, enabled) on a transition of a state in a UStateTree.

Returns: { tree_path, state_name, transition_index, trigger, priority, enabled, delay, delay_duration, saved }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
delayNoOptional whether to delay the transition
enabledNoOptional whether the transition is enabled
triggerNoOptional EStateTreeTransitionTrigger name (e.g. OnStateCompleted, OnTick)
priorityNoOptional EStateTreeTransitionPriority name (e.g. Low, Normal, High)
tree_pathYesAsset path to the UStateTree
state_nameYesName of the state owning the transition
delay_durationNoOptional delay duration in seconds (requires delay=true to take effect)
transition_indexNoIndex of the transition within the state

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=true, so the mutation/idempotency profile is covered. The description adds the returned shape, which is valuable since no output schema exists, and the 'saved' field hints the asset is persisted. It never explains what destructiveHint means here (overwriting existing property values) or what happens on an invalid transition_index.

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?

Two sentences, front-loaded with the action and affected fields. The return-value list is slightly boilerplate but earns its place because no output schema is provided.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose and return values, which is the bulk of what an 8-parameter mutation tool needs. Still missing how transition_index is obtained (e.g. via list_transitions), error behavior for a bad index, and whether setting properties marks the asset dirty or saves 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%, so the schema already documents all eight parameters with types and example values. The description only reiterates four of them (trigger, priority, delay, enabled) without adding format or constraint details beyond 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: setting trigger, priority, delay and enabled on a transition of a state in a UStateTree. That is far more specific than the name alone. It does not, however, distinguish itself from siblings like update_transition or remove_transition, so the agent must infer which mutator is appropriate.

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

Usage Guidelines2/5

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

There is no when-to-use / when-not-to-use guidance and no mention of alternatives such as update_transition, add_state_transition or remove_transition. The agent is left to infer that this tool only modifies an already-existing transition identified by transition_index.

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