Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_audio_section_start_offset

DestructiveIdempotent

Set the start offset for an audio section in a Unreal Engine Level Sequence to skip into the clip, using frames or seconds.

Instructions

Set the StartFrameOffset on an existing UMovieSceneAudioSection (skip-into-clip).

Returns: { sequence_path: string, section_index: int, old_start_offset_frames: int, new_start_offset_frames: int, applied: bool, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
section_indexNoIndex of the audio section on the audio track (default 0).
sequence_nameNoAlias for sequence_path.
sequence_pathNoAsset path of the Level Sequence.
start_offset_framesNoOptional raw frame offset (use for non-display-rate precision).
start_offset_secondsNoOptional offset in seconds (converted via display rate).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.2
    • removedInput schema / required
      Removed value: -[
-  "sequence_path",
-  "sequence_name"
-]
  2. First observedv1.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=true), and the description adds real behavioral value by disclosing the return payload — old/new offset frames plus applied, saved, and save_error — so the agent knows the change may not be persisted. It stops short of explaining why the operation is destructive or what save failure implies.

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?

It is two tight lines with the core operation front-loaded and the return shape second. No filler text, though the return contract could arguably be deferred to a structured field.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation tool with annotations covering safety and the schema covering all params, the definition is adequate: it names the target object and describes the response. The gap is the absence of any usage/precedence guidance for the two mutually-overlapping offset parameters, which an agent must resolve on its own.

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 coverage is 100%, so the schema already documents all five parameters, including the frame-vs-seconds distinction. The description only adds the 'skip-into-clip' semantic framing; it does not clarify the precedence/relationship between start_offset_frames and start_offset_seconds or the sequence_name alias. Baseline 3 is appropriate when the schema carries the load.

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 gives a specific verb+resource (set StartFrameOffset on an existing UMovieSceneAudioSection) and clarifies intent with 'skip-into-clip'. It is clearly distinguishable from adjacent audio-track tools like set_audio_track_volume, though it does not explicitly contrast with the nearest sibling set_audio_section_properties.

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 when-to-use guidance, no prerequisites (e.g., the sequence must be loaded/valid), and no statement about choosing between set_audio_section_properties and this narrower tool. Usage is only implied by the description's subject.

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