Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_event_track_section

Append a new event section to an existing UMovieSceneEventTrack on a Level Sequence, setting start and end frames to place gameplay event triggers.

Instructions

Append a new UMovieSceneEventSection to the existing UMovieSceneEventTrack on the sequence.

Returns: { sequence_path: string, track_class: string, section_index: int, section_count: int, start_frame: int, end_frame: int, section_class: string, section_added: bool, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_frameNoExclusive end frame for the new event section (default = start_frame + 1).
start_frameNoInclusive start frame for the new event section (default 0).
sequence_nameNoAlias for sequence_path.
sequence_pathNoAsset path of the Level Sequence.

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

A3.8/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, not idempotent, not destructive, closed-world). Beyond that, the description adds meaningful behavior by exposing a 'saved' flag and optional 'save_error' in the return, which tells the agent this operation writes the asset to disk and can fail on save. It does not say whether repeated calls create duplicate sections, which is the main remaining gap.

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 purpose is a single front-loaded sentence, and the return block is compact and functional rather than padding. Given there is no output schema, the inline return type earns its space; only minor verbosity in listing every return key.

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 4-parameter mutation tool with full schema coverage and annotations carrying the safety profile, the description covers the missing dimension: the return shape, which is absent as a structured output schema. Prerequisite context (the track must exist) is signalled, so an agent has enough to call it correctly.

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 all four parameters, including the sequence_name/sequence_path alias and the frame defaults, are already documented in the schema. The description adds no parameter-level meaning beyond echoing start_frame/end_frame in the return block, so the baseline of 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 names a specific verb (Append), the exact resource (UMovieSceneEventSection), and the parent it attaches to (an existing UMovieSceneEventTrack on the sequence). The word 'existing' implicitly separates it from add_event_track_to_sequence, but it never names that sibling, so the differentiation is only inferred.

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

Usage Guidelines3/5

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

Usage is implied by the prerequisite that the event track must already exist, but the description never states when to add a section versus creating a track, nor what happens if the track is absent. No alternatives or exclusions are given.

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