Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

configure_animation_events

DestructiveIdempotent

Enable, disable, or set custom tick and tick-when-paused behavior for a skeletal mesh component in Unreal editor or PIE worlds, returning previous and current flags.

Instructions

Switch the tick of a skeletal mesh component in the editor world (or the one the world param picks): despite the name, it only toggles component ticking and tick-when-paused. Returns the previous and current tick flags; nothing is marked dirty or saved.

Returns: { component_name: string, requested_settings: string, events_configured: bool, previous_tick_enabled: bool, previous_tick_when_paused: bool, current_tick_enabled: bool, current_tick_when_paused: bool, component_valid: bool, component_class: string, anim_instance_class: string?, has_anim_instance: bool, 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').
component_nameYesObject name of the USkeletalMeshComponent, e.g. "CharacterMesh0", case-insensitive; the first actor in the world that has one with that name wins
event_settingsYesTick mode, any case: 'enable' (tick on, not while paused), 'disable' (tick off) or 'custom' (tick on, paused setting kept)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • changedInput schema / properties / component_name / description
      Previous value: -"Name of the skeletal mesh component to configure"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"
    • changedInput schema / properties / event_settings / description
      Previous value: -"Event configuration mode: 'enable', 'disable', or 'custom'"New value: +"Tick mode, any case: 'enable' (tick on, not while paused), 'disable' (tick off) or 'custom' (tick on, paused setting kept)"
  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 mutation/readOnly and idempotency profile, so the description adds genuine extra context: 'nothing is marked dirty or saved' tells the agent the change is in-memory only despite destructiveHint=true, and it discloses that previous tick flags are returned. This is meaningful disclosure beyond the structured fields.

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-loaded with the core behavior and the name correction before the return detail. The inline Returns block is lengthy but justified because there is no output schema; every sentence carries real information.

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?

A mutating tool with no output schema, so the inline return-shape documentation and the 'nothing saved dirty' caveat close the main gaps. Coverage of world-selection behavior is present; what's missing is explicit alternative routing, which is minor.

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 world, component_name, and event_settings, including the enum. The description only nods at the 'world param' selection without adding syntax or semantics beyond the schema, so baseline 3 applies.

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 and resource: switching the tick flags of a skeletal mesh component. It also explicitly corrects the misleading name ('despite the name, it only toggles component ticking and tick-when-paused'), which lets an agent distinguish it from the anim-event tools among its siblings.

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?

It names the operating context ('editor world, or the one the world param picks') but gives no explicit when-to-use or when-not-to-use guidance and never routes the agent to a sibling (e.g. play_animation, set_bone_transform). Usage is implied rather than stated.

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