Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_transition_condition

Attach a reflection-based condition to a UStateTree transition using its struct name, tree path, state, and transition index; saves the updated tree.

Instructions

Attach a condition node (by struct name, via reflection) to a transition on a state of a UStateTree.

Returns: { tree_path, state_name, transition_index, condition_struct, condition_count, added, saved }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tree_pathYesAsset path to the UStateTree
state_nameYesName of the state owning the transition
condition_structYesCondition struct name or /Script path; must derive from StateTreeConditionBase (e.g. "StateTreeRandomCondition")
transition_indexNoIndex of the transition within the state (from get_state_tree_info)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / required
      Previous value: -[
-  "tree_path",
-  "condition_struct"
-]New value: +[
+  "tree_path",
+  "state_name",
+  "condition_struct"
+]
  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 the mutation profile (readOnly=false, idempotent=false, destructive=false). The description adds the return payload shape including "added" and "saved" flags, which is genuinely useful since there is no output schema, but it omits failure behavior and any authorization/precondition requirements.

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 compact sentences with the core action front-loaded and the return contract clearly separated. No filler; nothing important is buried.

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?

For a leaf mutation tool with annotations covering safety and no output schema, the description supplies the return fields and the resolution mechanism. It is close to complete, with minor gaps around preconditions and failure modes.

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 four parameters including the StateTreeConditionBase derivation constraint. The description only restates that the condition is resolved by struct name via reflection, adding marginal value over the schema.

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 ("Attach a condition node... to a transition on a state of a UStateTree") and clarifies the mechanism (by struct name, via reflection). It implicitly distinguishes from state-enter-condition siblings by scoping to a transition, but never names a sibling to route against.

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?

No when-to-use, when-not-to-use, or alternative is given. An agent cannot tell from the description whether this is the right tool versus add_state_enter_condition or set_condition_property, and prerequisites (compiled/saved tree, valid transition_index) are only hinted at via the schema.

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