Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_motion_warping_component_search_in_anims

DestructiveIdempotent

Enable or disable searching for motion-warping windows in animations nested inside montages on an actor's UMotionWarpingComponent, identified by internal name.

Instructions

Set bSearchForWindowsInAnimsWithinMontages on the UMotionWarpingComponent of an editor-world actor found by internal name (not label): when true, warping windows are also searched in animations inside montages. Marks the level dirty, not saved; returns previous and new values and changed.

Returns: { actor_name, previous_search_in_anims: bool, new_search_in_anims: bool, changed: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enabledYesSets bSearchForWindowsInAnimsWithinMontages: when true, motion-warping windows are also searched in animations nested inside montages (required, no default)
actor_nameYesInternal object name of the actor with the UMotionWarpingComponent, e.g. "BP_Hero_C_0"; the outliner label does not match.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / actor_name / description
      Previous value: -"Engine name of the actor carrying the UMotionWarpingComponent"New value: +"Internal object name of the actor with the UMotionWarpingComponent, e.g. \"BP_Hero_C_0\"; the outliner label does not match."
  2. First observedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnly=false, destructive=true, idempotent=true). The description adds non-obvious behavioral context beyond that: it marks the level dirty but does not save, and it returns previous/new values plus a changed flag. This is genuinely useful for an agent planning a mutation.

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?

The primary sentence is front-loaded and dense with meaningful detail, followed by a compact returns summary. It is slightly packed for one sentence but no line is wasted.

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 no output schema, the description compensates by describing the return shape, and it notes the dirty-but-unsaved persistence behavior. Annotations cover the safety profile and the schema covers the params, so the definition is essentially complete for this 2-parameter mutation.

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 both parameters are already documented in the schema, including the internal-name caveat and the enabled semantics. The description restates these meanings but adds little beyond what the schema provides, which matches the baseline of 3 when the schema carries the load.

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 states a precise verb (Set) and a fully-qualified resource: bSearchForWindowsInAnimsWithinMontages on the UMotionWarpingComponent of an actor. It also spells out the flag's semantics and the lookup method (internal name, not label), which cleanly separates it from sibling motion-warping tools like set_motion_warping_target_* and inspect_motion_warping_component.

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

Usage Guidelines3/5

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

Usage is implied by the phrasing (editor-world actor, found by internal name), and no direct alternatives are named. There is no explicit when-to-use versus when-not-to-use guidance or reference to a sibling this should replace. Adequate but with a clear gap.

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