Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

stop_animation

Destructive

Halts AnimMontage playback on a skeletal mesh component with a 0.25s blend-out. Stops a specified montage or all active montages in editor or chosen world.

Instructions

Stop montage playback on a skeletal mesh component with Montage_Stop and a 0.25 s blend-out: only montage_path when given, otherwise every active montage. Editor world unless the world param says otherwise; an unknown montage_path is an error. was_playing and playing cover any montage.

Returns: { component_name: string, was_playing: bool, playing: bool, success: bool, montage_path: string?, montage_name: string?, world: string, world_name: string|null, world_package: string|null, world_type: string|null, net_mode: string|null, pie_instance: number }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
worldNoOptional world selector: absent/'editor' (default) | 'pie' (ambiguous: PlayWorld, else the first PIE context) | 'server' (the PIE world with authority) | 'client' | 'pie:N' | 'game' (alias of 'pie').
montage_pathNoFull asset path of a specific AnimMontage to stop; if omitted, stops all montages (optional)
component_nameYesObject name of the USkeletalMeshComponent, e.g. "CharacterMesh0", case-insensitive; the first actor in the world that has one with that name wins

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / component_name / description
      Previous value: -"Name of the skeletal mesh component to stop animation on"New value: +"Object name of the USkeletalMeshComponent, e.g. \"CharacterMesh0\", case-insensitive; the first actor in the world that has one with that name wins"
  2. First observedv1.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=false, readOnly=false, so the safety profile is covered; the description adds real behavioral detail: a 0.25 s blend-out, that an unknown montage_path is an error, and the editor-world default. It does not state permission/auth requirements, but the added context is substantive.

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?

Front-loads the action and scope in the first sentence, then covers world selection and errors. The inline return-shape listing is long but earns its place given there is no output schema. Slightly dense but no wasted filler.

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 destructive mutation tool it covers scope, defaults, error behavior, and return fields (needed since no output schema exists). Annotations already carry the safety profile. Only minor gaps remain, such as any permission prerequisites.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, giving a baseline of 3, and the description adds value by clarifying the omission semantics of both optional params (omit montage_path = stop all; omit world = editor world) and that an unknown montage_path errors. That is meaningful meaning beyond the schema's per-field prose.

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?

States a specific verb (stop) and resource (montage playback on a skeletal mesh component), naming the underlying Montage_Stop operation and the 0.25 s blend-out. An agent can distinguish it from siblings like play_animation, get_active_montages, and remove_anim_montage without opening any schema.

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

Usage Guidelines4/5

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

Clearly describes the two invocation modes: stop only montage_path when supplied, otherwise stop every active montage, and notes the default editor world. It implies context well but never names an explicit alternative tool or a when-not-to-use condition, so it stops short of full routing guidance.

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