Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_skeletal_animation_section_params

DestructiveIdempotent

Set playback parameters on a skeletal-animation section, including reverse, play rate, slot name, and frame offsets. Directly writes FMovieSceneSkeletalAnimationParams fields for precise control.

Instructions

Set the playback params on a skeletal-animation section (UMovieSceneSkeletalAnimationSection::Params). Writes the public FMovieSceneSkeletalAnimationParams fields directly.

Returns: { sequence_path: string, section_index: int, reverse: bool, slot_name: string, start_frame_offset: int, end_frame_offset: int, skip_anim_notifiers: bool, force_custom_mode: bool, play_rate: double|null, set: bool, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reverseNobReverse (omit to leave unchanged).
play_rateNoConstant playback rate (double; must be non-zero -- ~0 is a FixedTime warp, not a play rate; omit to leave unchanged).
slot_nameNoSlotName (FName; omit to leave unchanged).
track_typeNoOptional class filter (default resolves the skeletal-animation track; see set_section_easing).
track_indexNoIndex into the binding's tracks (default 0).
binding_guidNoGUID of the binding whose skeletal-animation section to edit.
section_indexNoIndex of the section on the resolved track (default 0).
sequence_nameNoAlias for sequence_path.
sequence_pathNoFull /Game path OR bare asset name of the target Level Sequence.
end_frame_offsetNoEndFrameOffset in tick frames (omit to leave unchanged).
force_custom_modeNobForceCustomMode (omit to leave unchanged).
start_frame_offsetNoStartFrameOffset in tick frames (omit to leave unchanged).
skip_anim_notifiersNobSkipAnimNotifiers (omit to leave unchanged).
binding_name_or_guidNoAlias for binding_guid, read only when binding_guid is absent; it must also be a GUID string, a bound object's name is not resolved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • changedInput schema / properties / binding_name_or_guid / description
      Previous value: -"Sequencer binding: the bound object's name or its GUID string."New value: +"Alias for binding_guid, read only when binding_guid is absent; it must also be a GUID string, a bound object's name is not resolved."
    • removedInput schema / required
      Removed value: -[
-  "sequence_path",
-  "binding_guid"
-]
  2. 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 destructiveHint=true and idempotentHint=true, so the agent knows this mutates and is replayable. The description adds that it 'writes the public ... fields directly,' which is useful mutation context, but says nothing about permissions, side effects on other sections, or save behavior despite the destructive flag.

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 in the first sentence and keeps prose tight, though the trailing Returns block is a large object dump that could arguably be trimmed given no output schema exists to compare against.

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 14-parameter mutation tool with full schema coverage and no output schema, the description plus the included Returns shape give an agent enough to call it correctly. It lacks only risk/permission framing for a destructive write.

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 all 14 parameters, including the 'omit to leave unchanged' semantics and aliases, are already documented in the schema. The description adds no parameter meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 (Set) and resource (playback params on a skeletal-animation section), and even names the underlying class UMovieSceneSkeletalAnimationSection::Params. Clear and precise, but it does not differentiate itself from the many sibling set_section_* tools (set_section_easing, set_section_range, etc.) that an agent could confuse it with.

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?

No when-to-use guidance, no prerequisites, and no routing to alternatives. The only sibling mention, 'see set_section_easing,' appears inside the track_type schema description, not the tool description, so the description itself gives no selection context.

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