Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_transform_section_mask

DestructiveIdempotent

Set the evaluation channel mask on a 3D transform section to enable specific transform channels (translation, rotation, scale) for evaluation without deleting keys.

Instructions

Set the evaluation channel mask on a 3D transform section (UMovieScene3DTransformSection::SetMask). The mask is a visibility/eval filter built from EMovieSceneTransformChannel; it nulls the channel proxy (intended rebuild) and does NOT delete existing keys.

Returns: { sequence_path: string, section_index: int, channels: string[], channel_mask: int, set: bool, saved: bool, note: string, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelsNoChannels to ENABLE: a JSON array (e.g. ["TranslationX","Rotation"]) OR a comma-separated string. Tokens: TranslationX/Y/Z, Translation, RotationX/Y/Z (Roll/Pitch/Yaw), Rotation, ScaleX/Y/Z, Scale, Weight, AllTransform, All, None.
track_typeNoOptional class filter (default resolves the transform track; see set_section_easing).
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.
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

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real substance: the mask is a visibility/eval filter, it nulls the channel proxy (an intended rebuild), and it does NOT delete existing keys. That tells the agent exactly what is mutated and what is preserved, which the annotations alone cannot convey.

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?

The action and its key caveat are front-loaded, and the Returns block is justified because no output schema exists. Sentence count is modest and each element carries information, though the C++ symbol reference is somewhat incidental.

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, 8-parameter mutation tool with no output schema, the description covers the operation, its side effects on keys, and the return shape. It omits prerequisites (e.g., that the transform section must already exist and how the track is resolved), which is a minor gap.

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 fully documents all 8 parameters, including the channel token list. The description adds no parameter-specific syntax or defaults beyond that, so the baseline 3 applies.

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?

The description states a specific verb and resource: setting the evaluation channel mask on a 3D transform section, with the underlying C++ member named. An agent can distinguish it from sibling transform-section tools like set_transform_section_quaternion_interp. It stops short of explicitly naming which sibling to prefer, keeping it out of the top band.

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?

There is no statement of when to use this tool versus alternatives such as set_transform_track_interp_mode or the keyframe tools. The note about not deleting keys is behavioral, not usage routing, so the agent is left to infer the scenario on its own.

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