Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_sequence_view_range

DestructiveIdempotent

Set the visible Sequencer timeline window for a Level Sequence in seconds, adjusting only the editor view range without altering playback or persisting changes.

Instructions

Sets the editor view range of a Level Sequence (path or bare asset name), in seconds: the visible window of the Sequencer timeline. Editor UI state only, it changes neither playback nor the playback range. The engine keeps it in a transient field, so it lasts for this editor session and is not saved (persisted is always false); a Sequencer showing the sequence follows it on its next tick. Undoable, and the package is not marked dirty. verified compares the stored range with the request. For the scrollable bounds use set_sequence_working_range; for what plays use set_sequence_playback_range.

Returns: { sequence_path: string, start_seconds: float, end_seconds: float, verified: bool, persisted: bool (always false: the field is transient) }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_secondsYesEnd of the view range, in seconds. Must be > start_seconds.
sequence_nameNoAlias for sequence_path.
sequence_pathNoAsset path of the Level Sequence.
start_secondsYesStart of the view range, in seconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / required
      Previous value: -[
-  "sequence_path",
-  "start_seconds",
-  "end_seconds"
-]New value: +[
+  "start_seconds",
+  "end_seconds"
+]
  2. First observedv1.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover safety hints, but the description adds substantial context beyond them: editor-UI-only scope, transient non-persisted field (persisted always false), next-tick follow behavior, undoability, and that the package is not marked dirty. These are exactly the traits an agent needs before mutating editor state.

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 purpose and the sibling disambiguation, and nearly every sentence carries non-obvious information. It is on the long side, but because there is no output schema the returns block earns its place.

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?

Covers purpose, alternatives, persistence semantics, undo behavior, and return shape for a state-mutating editor tool. Nothing an agent needs to invoke it 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 100%, so the baseline is 3, but the description adds meaning the schema does not: sequence_path accepts 'path or bare asset name', and units are seconds throughout. The 'verified compares the stored range with the request' note clarifies the verification behavior associated with the call.

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 ('Sets the editor view range of a Level Sequence') and immediately scopes it as 'the visible window of the Sequencer timeline', which is enough to distinguish it from set_sequence_working_range and set_sequence_playback_range without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'For the scrollable bounds use set_sequence_working_range; for what plays use set_sequence_playback_range.' Both the alternative tools and the selecting condition are named, leaving nothing to inference.

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