Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_attach_section_rules

DestructiveIdempotent

Set attach and detach transform rules for a Sequencer 3D-attach section to control how an actor's location, rotation, and scale are preserved when attachment starts or ends.

Instructions

Set the attach/detach transform rules on a Sequencer 3D-attach section (created by add_attach_track). The 6 rules (location/rotation/scale x attach/detach) control how the attachee's transform is preserved when the attach begins/ends. Only the supplied rules change (applied_count) and all 6 are read back. The section is resolved like get_section_info (binding_guid + track_index + section_index).

Returns: { sequence_path: string, attach_rules: object, applied_count: int, applied: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_typeNoOptional class filter to pick the track ("transform"|"float"|"bool"|"vector"|"color"|"visibility"|"audio"|"event"|"fade"|"skeletalanimation"|"subsequence"|"cameracut"|"property"); used when track_index is omitted.
track_indexNoOptional index into the binding's tracks (default 0).
binding_guidNoGUID of the attachee binding that owns the attach track.
section_indexNoOptional index of the section on the track (default 0).
sequence_nameNoName of the target Level Sequence (or sequence_path).
sequence_pathNoAsset path of the target Level Sequence (alias for sequence_name).
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.
attachment_scale_ruleNoOptional EAttachmentRule: KeepRelative | KeepWorld | SnapToTarget.
detachment_scale_ruleNoOptional EDetachmentRule: KeepRelative | KeepWorld.
attachment_location_ruleNoOptional EAttachmentRule: KeepRelative | KeepWorld | SnapToTarget.
attachment_rotation_ruleNoOptional EAttachmentRule: KeepRelative | KeepWorld | SnapToTarget.
detachment_location_ruleNoOptional EDetachmentRule: KeepRelative | KeepWorld.
detachment_rotation_ruleNoOptional EDetachmentRule: KeepRelative | KeepWorld.

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 (alias for binding_guid)."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

A4.1/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing partial-update semantics (only supplied rules change; applied_count reflects this) and that all 6 rules are read back, which explains the idempotentHint and 'applied' result. The destructiveHint=true is not explained, but the description usefully clarifies the mutation's granularity and the section-resolution requirement.

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 verb+resource, then the rule semantics, then resolution, then the return shape. Two tight sentences plus one returns line with no filler. Slightly dense but every clause carries 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?

With no output schema present, the description voluntarily documents the return shape (sequence_path, attach_rules, applied_count, applied, save_error). It covers the prerequisite, resolution scheme, and partial-update semantics for a 13-param mutation, leaving only the reason for destructiveHint unstated.

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 every one of the 13 parameters is already documented, including aliases and enums. The description only restates the section-resolution trio and the six rules, adding no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 (Set) and resource (attach/detach transform rules on a Sequencer 3D-attach section), and explicitly names the sibling that creates the target (add_attach_track). The '6 rules (location/rotation/scale x attach/detach)' phrase makes the scope unambiguous and distinguishable from other section-setters like set_section_range.

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

Usage Guidelines4/5

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

Gives clear context: the section must originate from add_attach_track, and the section is resolved the same way as get_section_info (binding_guid + track_index + section_index). It also clarifies partial-update behavior ('Only the supplied rules change'). It stops short of naming when-not or alternative tools, so it is not a full 5.

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