Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_transform_section_quaternion_interp

DestructiveIdempotent

Enable or disable quaternion (slerp) rotation interpolation for a Level Sequence transform section, with keys preserved and the sequence saved in an undo transaction.

Instructions

Turns quaternion (slerp) rotation interpolation on or off for one 3D transform section of a Level Sequence binding, in an undo transaction, and saves the sequence; keys are kept. The section is section_index on the binding's first track of track_type, or on its track_index-th track when track_type is omitted or unrecognised; a section that is not a 3D transform section is an error. For the section's blend type use set_transform_track_interp_mode; to enable or disable channels use set_transform_section_mask.

Returns: { sequence_path: string, section_index: int, use_quaternion_interpolation: bool, set: bool, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_typeNoOptional track kind, e.g. "transform": picks the binding's first track of that kind. Omitted or unrecognised, track_index picks the track instead.
track_indexNoIndex into the binding's tracks (default 0).
binding_guidNoGUID of the binding whose transform 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.
use_quaternionYesDesired quaternion-interpolation state.
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. Changed3 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."
    • changedInput schema / properties / track_type / description
      Previous value: -"Optional class filter (default resolves the transform track)."New value: +"Optional track kind, e.g. \"transform\": picks the binding's first track of that kind. Omitted or unrecognised, track_index picks the track instead."
    • changedInput schema / required
      Previous value: -[
-  "sequence_path",
-  "binding_guid",
-  "use_quaternion"
-]New value: +[
+  "use_quaternion"
+]
  2. First observedv1.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations cover mutation/idempotence/destructiveness, and the description adds genuine context beyond them: the operation runs in an undo transaction, saves the sequence to disk, preserves keys, and errors on a wrong section type. It even clarifies what is NOT destroyed ('keys are kept'), resolving the destructiveHint ambiguity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core action, then resolution rules, then alternatives, then a Returns block. Every sentence carries information; nothing is redundant padding, and the Returns block compensates for the absent output schema.

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?

Complete for a mutation tool: safety profile is in annotations, output shape is given inline despite no output schema, parameter interaction is explained, and sibling alternatives plus error conditions are stated. Nothing needed to call it correctly is missing.

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%, so the schema already documents each field and the baseline is 3. The description adds value by synthesizing the resolution rule across track_type/track_index/section_index into one coherent precedence statement, which helps an agent invoke the locator params correctly.

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 precise verb+resource+scope: turning quaternion/slerp rotation interpolation on/off for one 3D transform section of a Level Sequence binding. It also names the sibling tools it is NOT (set_transform_track_interp_mode, set_transform_section_mask), so an agent can distinguish it without opening schemas.

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

Usage Guidelines5/5

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

Explicitly routes to alternatives and their distinct scopes: blend type goes to set_transform_track_interp_mode, channel enable/disable goes to set_transform_section_mask. It also states a negative condition (a non-3D-transform section is an error) and the side effects (undo transaction, auto-save, keys kept).

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