Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_anim_transition_rule_from_comparison

DestructiveIdempotent

Wire a float comparison as an AnimBP state machine transition rule between source and target states, using a variable, operator, and value; saves and verifies.

Instructions

Wire a float comparison as the rule of a transition.

Returns: { anim_blueprint_path, machine_name, source_state, target_state, variable_name, operator, comparison_value, variable_kind, rule_set, sink_present, contributor_count, contributor_node_classes, saved, save_error? }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoOptional. This command is REFUSED while a Play-in-Editor session is running: it either compiles a Blueprint (the reinstancer can retain a world, and CheckForWorldGCLeaks is Fatal -- it KILLS the editor) or writes to disk (Editor.AllowSavingAssetsDuringPIE=0 makes the engine refuse the write, so it would report success without writing a byte). Stop PIE and retry instead; force=true runs it anyway, at your own risk.
operatorYesOne of "==", "!=", ">", "<", ">=", "<=" (compared against comparison_value)
to_stateNoAlias of `target_state` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `target_state`.
from_stateNoAlias of `source_state` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `source_state`.
machine_nameYesName of the state machine that owns the transition
source_stateNoName of the source state (transition origin)
target_stateNoName of the target state (transition destination)
variable_nameYesName of an existing float variable on the AnimBP (or its parent C++ class)
blueprint_nameNoAlias of `anim_blueprint_path` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `anim_blueprint_path`.
comparison_valueNoFloat literal on the right-hand side of the comparison
anim_blueprint_pathNoAsset path of the UAnimBlueprint

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 safety profile is covered. The description adds the return payload fields (rule_set, sink_present, contributor_count, saved, save_error?), which is genuine behavioral value since no output schema exists. It does not restate or contradict the annotations.

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 with the action front-loaded and no filler. The return-value block is a dense field dump rather than prose, but for a tool with no output schema that is a reasonable use of space.

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?

With 100% schema coverage and 11 parameters, the schema carries the input burden, and the description supplies the return shape the absent output schema would otherwise provide. The one gap is that the PIE-refusal constraint (the most consequential behavior for a destructive write) lives only in the schema's `force` text rather than in the description.

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 all 11 parameters (including the from_state/to_state/blueprint_name aliases and the detailed `force` PIE warning) are documented in the schema. The description adds no parameter syntax or meaning beyond what the schema provides, so the baseline of 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 ('Wire') and resource ('a float comparison as the rule of a transition'), which is precise enough to separate it from siblings like set_anim_transition_rule_from_bool and set_anim_transition_rule_automatic by the kind of rule being created. It does not name those siblings explicitly, but the 'float comparison' qualifier carries the differentiation.

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?

The description gives no when-to-use or when-to-avoid guidance and no prerequisites. The important PIE-refusal condition is documented in the schema's `force` parameter, not in the description text the agent reads first, and no alternative tool is mentioned.

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