Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

clear_anim_transition_rule

DestructiveIdempotent

Removes all rule nodes from an animation state machine transition's BoundGraph, leaving only the sink node, so you can reset or replace transition logic.

Instructions

Remove every rule node from a transition's BoundGraph except the sink.

Returns: { anim_blueprint_path, machine_name, source_state, target_state, rule_cleared, sink_present, removed_count, remaining_rule_nodes, 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.
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)
blueprint_nameNoAlias of `anim_blueprint_path` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `anim_blueprint_path`.
anim_blueprint_pathNoAsset path of the UAnimBlueprint

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true and readOnly=false, so the safety profile is covered. The description adds genuinely new behavioral detail beyond them: the sink node is intentionally preserved (so the transition survives), and it discloses the exact return payload including removed_count and remaining_rule_nodes. It omits any auth/compile-state requirements, keeping it short of a 5.

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 well-separated blocks: the one-line purpose first, then the return shape. No filler prose. The Returns enumeration is slightly long but is the only return documentation available, so it earns its place.

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?

No output schema exists, so the description supplies the return shape itself, which is the key missing piece. Combined with annotations carrying safety and a 100%-documented 8-parameter schema, an agent has enough to call this mutation correctly.

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 the schema itself carries rich semantics (force/PIE-refusal, alias parameters, path meaning). The description adds no parameter-level meaning beyond what the schema already provides, so the baseline of 3 for fully documented schemas is correct.

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 (Remove) and a precise resource (every rule node from a transition's BoundGraph), and the 'except the sink' qualifier pins down the exact scope. It is clearly distinguishable from siblings like remove_anim_transition (removes the whole transition) and the set_anim_transition_rule_* family, though it never names those siblings explicitly.

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 guidance, no prerequisites, and no mention of alternatives. The agent must infer that this is the 'wipe the rules' operation versus set_anim_transition_rule_from_bool or remove_anim_transition entirely on its own.

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