Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_shot_section

Add a cinematic shot section to a Level Sequence's shot track and save it, creating the missing track or inner shot sequence as required.

Instructions

Adds a cinematic shot section (UMovieSceneCinematicShotSection) to the shot track and saves the sequence. Creates the cinematic shot track if it does not exist yet. The inner shot sequence is shot_sequence_path, or _Shot in the target's folder when omitted; it is loaded when it exists, else created and saved as a new asset (inner_sequence_created says which). An inner shot sequence that cannot be loaded, created or saved (a new one that fails to save stays in memory only), that is the target itself or that already plays it at any depth is an error and nothing is added. success is false, with save_error, when the save of the target fails.

Returns: { sequence_path: string, track_class: string, track_added: bool, section_added: bool, inner_sequence_created: bool (true only when this call created the inner sequence), shot_name: string, shot_sequence_path: string, start_frame: int, duration: int, section_count: int, section_class: string, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
durationNoSection duration in tick frames (default 150).
start_frameNoInclusive start frame for the shot section (default 0).
sequence_nameNoAlias for sequence_path.
sequence_pathNoFull /Game path OR bare asset name of the target Level Sequence.
shot_sequence_pathNoOptional content path of the inner shot Level Sequence. If omitted, an inner shot Level Sequence is created and persisted.

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

A4.6/5.0
Behavior5/5

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

Annotations are thin (non-readOnly, non-idempotent), so the description carries real weight and delivers: track auto-creation, inner-sequence load-or-create semantics, the in-memory-only failure case, and the error/no-op behavior with save_error. This is unusually rich disclosure of side effects and failure modes.

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-loaded with the effect and scope, followed by defaults, error conditions, and a return shape. Dense but every clause carries distinct behavioral information; the long single-sentence Returns block is justified because no output schema exists.

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?

Despite has_output_schema being false, the description inlines the full return structure and the success/save_error contract, plus the failure and no-op conditions. Nothing an agent needs to call this mutation tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3. The description goes further by explaining what shot_sequence_path omission actually does (defaults to <target name>_Shot in the target's folder) and ties start_frame/duration to the produced section, adding meaning beyond the schema text.

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 and resource ('Adds a cinematic shot section (UMovieSceneCinematicShotSection) to the shot track and saves the sequence'), and distinguishes itself from the sibling add_shot_track by noting it creates the track if missing. An agent can identify exactly what this tool produces without opening the schema.

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?

Conveys strong usage context: the shot track is auto-created if absent, the inner shot sequence is loaded when it exists or created/ saved when it does not, and certain inner-sequence conditions are errors. It never explicitly names an alternative tool or a when-not-to-use condition, so it stops short of a 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