Skip to main content
Glama

add_attach_track

Idempotent

Attach one object to another in a Level Sequence via a 3D-Attach track, so it follows the target over a frame range (e.g., prop to hand socket).

Instructions

Add a Sequencer 3D-Attach track on a binding so it follows another binding (e.g. a prop attached to a character's hand socket) over the section's range. The attachee binding owns a UMovieScene3DAttachTrack; AddConstraint creates an attach section pointing at the target binding. Idempotent by (target_binding_guid, start_frame).

Returns: { sequence_name: string, binding_guid: string, target_binding_guid: string, track_added: bool, already_exists: bool, start_frame: int, duration: int, socket_name: string, component_name: string, section_count: int, track_class: string, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
durationNoOptional duration in frames (default: the playback range size).
socket_nameNoOptional socket name on the target to attach to (default: none -> target root).
start_frameNoOptional start frame of the attach section (default: the sequence playback range start).
binding_guidYesGUID of the binding to attach (the attachee; this binding owns the attach track).
sequence_nameYesName of the target Level Sequence.
component_nameNoOptional component name on the target to attach to (default: none).
target_binding_guidYesGUID of the binding to attach TO (the parent/target).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false and idempotentHint=true; the description adds the exact idempotency key '(target_binding_guid, start_frame)', which is more actionable than the boolean hint, plus the side effect that an attach section is created. It stops short of noting auth/permission needs or save behavior details, keeping it below a 5.

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?

Purpose is front-loaded in the first clause, and the mechanical explanation and return shape follow in a logical order. The results block is verbose but justified since there is no output schema; overall it stays tight with no filler.

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?

A 7-parameter mutation tool with no output schema; the description compensates by enumerating the return object (including save_error) and explaining the attach mechanism. It is essentially complete, with only minor gaps around failure/save semantics.

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 baseline is 3. The description lightly reinforces socket_name via the 'hand socket' example and start_frame via the idempotency key, but adds little syntax or default semantics beyond what the schema already documents.

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+resource ('Add a Sequencer 3D-Attach track on a binding') and names the concrete mechanism (UMovieScene3DAttachTrack, attach section pointing at a target binding). This cleanly separates it from the crowded add_*_track siblings (add_transform_track_to_binding, add_weighted_value_track, add_visibility_track) that share the 'add a track' shape.

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?

Clear context is given via the motivating example ('a prop attached to a character's hand socket'), which tells the agent when this is the right tool. However, it never names alternatives (e.g. attach_actor, add_transform_track_to_binding, set_attach_section_rules) or states exclusions, so the agent must infer the choice.

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