Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_section_row_index

DestructiveIdempotent

Set the row index of a Sequencer section to arrange clips across multiple rows. Only applies to tracks that support multiple rows and marks the track as modified.

Instructions

Set the row index of a sequencer section (UMovieSceneSection::SetRowIndex). Only meaningful when the owning track supports multiple rows (reported as supports_multiple_rows); the owning track is also Modify()'d.

Returns: { sequence_path: string, section_index: int, row_index: int, supports_multiple_rows: bool, set: bool, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
row_indexYesDesired row index (int, >= 0).
track_typeNoOptional class filter (see set_section_easing).
track_indexNoIndex into the binding's tracks (default 0).
binding_guidNoGUID of the binding whose section to edit.
section_indexNoIndex of the section on the resolved track (default 0).
sequence_nameNoAlias for sequence_path.
sequence_pathNoFull /Game path OR bare asset name of the target Level Sequence.
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.

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."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."
    • changedInput schema / required
      Previous value: -[
-  "sequence_path",
-  "binding_guid",
-  "row_index"
-]New value: +[
+  "row_index"
+]
  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?

Annotations already declare non-read-only, idempotent, destructive behavior, so the bar is lower, and the description adds real value beyond them: it discloses the side effect that the owning track is Modify()'d, and the return fields (saved, save_error) imply an auto-save step. It does not detail rollback semantics or what 'destructive' means here.

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?

Two tight sections with the core action and its precondition front-loaded, and the return shape appended. The Returns block earns its place because no output schema exists, though it slightly lengthens the definition.

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?

For an 8-parameter mutation tool with no output schema, the description supplies the missing return contract inline and covers the key behavioral precondition and side effect. It leaves minor gaps around error modes (other than save_error) and required permissions, but is largely sufficient for correct invocation.

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% and each of the 8 parameters is documented in the schema, so the baseline of 3 applies. The description adds no parameter-specific meaning beyond a cross-reference to set_section_easing for track_type, and the required row_index intent is already captured in the schema.

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 precise verb and resource ('Set the row index of a sequencer section') and even cites the engine method (UMovieSceneSection::SetRowIndex), making it trivially distinguishable from sibling setters like set_section_easing or set_section_color. An agent can tell exactly what object and property is being changed.

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?

Provides a clear precondition: the tool is 'only meaningful when the owning track supports multiple rows (reported as supports_multiple_rows)', which routes the agent to check a signal first. It does not name alternative tools for the single-row case, so it falls short of explicit when-not/alternatives guidance.

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