Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_sequence_working_range

DestructiveIdempotent

Set the scrollable working range for a Level Sequence in Sequencer, in seconds. Adjusts editor UI session state only; playback and saved data are unaffected.

Instructions

Sets the working range of a Level Sequence (path or bare asset name): the scrollable bounds of the Sequencer timeline, in seconds. Editor UI state only, it changes neither playback nor evaluation. The engine keeps it in a transient field, so it lasts for this editor session and is not saved (persisted is always false): after a reload the working range is recomputed from the playback range. Undoable, and the package is not marked dirty. verified compares the stored range with the request. For the visible window use set_sequence_view_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 working range, in seconds. Must be > start_seconds.
sequence_nameNoAlias for sequence_path.
sequence_pathNoAsset path of the Level Sequence.
start_secondsYesStart of the working 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.4/5.0
Behavior3/5

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

Very strong disclosure beyond annotations: transient field, session-only lifetime, not persisted, recomputed from playback range after reload, undoable, package not dirtied, and what verified compares. However, the annotations declare destructiveHint=true while the description emphasizes that nothing is changed in playback/evaluation and the package is not dirtied — a tension, though not a direct contradiction, since the tool does mutate state and is undoable. Scoring 3 rather than 5 reflects that unresolved conflict with the destructive annotation.

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-loads the core action, then lifetime, then undo/dirty semantics, then sibling routing, then return shape. Dense but every sentence carries information; the parenthetical about persisted=false is slightly redundant with the Returns block.

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?

No output schema exists, so the inline Returns block (sequence_path, start_seconds, end_seconds, verified, persisted) closes the gap. Combined with the lifetime and undo disclosures, an agent has everything needed to call and interpret this correctly.

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 3 baseline applies, but the description adds meaning: it clarifies that sequence_path accepts 'a path or bare asset name' and documents the seconds unit and the start/end relationship at the tool level. That is a genuine increment over the schema's per-parameter 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 ('Sets the working range of a Level Sequence') and immediately bounds the scope in seconds as the scrollable bounds of the Sequencer timeline. It distinguishes itself from the two nearest siblings by name, so an agent can route without reading sibling schemas.

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 visible window use set_sequence_view_range; for what plays use set_sequence_playback_range.' This is the exact when-to-use/when-to-use-something-else guidance the dimension asks for.

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