Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_transform_track_interp_mode

DestructiveIdempotent

Set a Level Sequence section's blend type to control how it layers with other sections; validates support, applies in an undo transaction, and saves the sequence.

Instructions

Sets the blend type of one section on a Level Sequence binding (how it layers with other sections, e.g. additive adds a delta, override replaces), in an undo transaction, and saves the sequence. Despite the name it changes no key interpolation and accepts any track kind. The section is section_index on the binding's first track of track_type, else its track_index-th track; a blend type the track does not support is refused. set_section_blend_type does the same without that check; for slerp rotation use set_transform_section_quaternion_interp.

Returns: { sequence_path: string, interp_mode: string, blend_type: string, blend_type_valid: bool, applied: bool, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
blend_typeNoAlias for interp_mode (absolute|additive|relative|additive_from_base|override)
track_typeNoOptional track kind such as "transform", "float" or "audio": picks the binding's first track of that kind. Omitted or unrecognised, track_index picks the track instead.
interp_modeNoBlend type string; one of absolute|additive|relative|additive_from_base|override. Also accepted under "blend_type".
track_indexNoIndex into the binding's tracks (0 = first track, default 0).
binding_guidNoGUID of the binding the section lives under.
section_indexNoIndex of the section on the resolved track (default 0).
sequence_nameNoAlias for sequence_path.
sequence_pathNoAsset path of the Level Sequence.
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 (defaults to transform track lookup)."New value: +"Optional track kind such as \"transform\", \"float\" or \"audio\": picks the binding's first track of that kind. Omitted or unrecognised, track_index picks the track instead."
    • removedInput schema / required
      Removed value: -[
-  "sequence_path",
-  "binding_guid",
-  "interp_mode"
-]
  2. First observedv1.1.0

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already declare the mutation profile (readOnly=false, destructive=true, idempotent=true), but the description adds operational behavior they don't cover: it runs in an undo transaction, saves the sequence, and refuses unsupported blend types. It stops short of explaining what the destructive hint actually affects or what happens to the asset on save failure, so not a full 5.

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 action and its blend-layer meaning, then the name caveat, then the resolution rule, then alternatives, then the return shape. Every sentence carries distinct information with no padding.

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?

For a 9-parameter mutation with no output schema, the description supplies the return shape, the parameter coupling rules, the failure condition, and the adjacent alternatives, which is sufficient for an agent to call it correctly.

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?

With 100% schema coverage the baseline is 3, and the description adds a real semantic layer: section_index resolves against the first track of track_type or the track_index-th track, and the blend type must be track-supported or the call fails. The alias mechanics are already in the schema, so this is enrichment rather than uncompensated gaps.

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?

Names a specific verb and resource (sets one section's blend type on a Level Sequence binding) and preempts the misleading name by stating it changes no key interpolation and accepts any track kind. It explicitly contrasts with set_section_blend_type and set_transform_section_quaternion_interp, so the agent can separate it from its neighbors.

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?

Gives explicit routing: use set_section_blend_type when the support check is unwanted, and set_transform_section_quaternion_interp for slerp rotation. It also states the precondition that an unsupported blend type is refused, which tells the caller when this tool will fail rather than silently act.

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