Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_section_locked

DestructiveIdempotent

Lock or unlock a sequencer section in Unreal Engine to prevent or allow edits; lock last in an edit chain so other operations cannot modify it.

Instructions

Lock or unlock a sequencer section. Maps to UMovieSceneSection::SetIsLocked; a locked section cannot be modified by other edit ops, so lock LAST in an edit chain.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lockedYesDesired locked state.
track_typeNoOptional class filter (see set_section_easing).
track_indexNoIndex into the binding's tracks (0 = first track, 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",
-  "locked"
-]New value: +[
+  "locked"
+]
  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 readOnly=false, destructive=true, idempotent=true, openWorld=false. The description goes beyond them by explaining the consequence of the state change (locked sections resist other edit ops), which is the key behavioral trait an agent needs to sequence its calls. It also discloses the return payload despite there being no output schema.

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 short, front-loaded sentences. The purpose comes first and the ordering constraint immediately follows. The inline 'Returns:' block is dense and slightly interrupts the prose, but it is information-dense rather than wasteful.

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 a mutation tool with no output schema, the description supplies the missing return shape and the critical sequencing rule, and annotations cover the safety profile. Parameter documentation is fully handled by the schema. Only the absence of explicit sibling alternatives keeps it from top marks.

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 all 8 parameters are already documented in the schema (including the binding_guid/binding_name_or_guid alias rule). The description adds no parameter-level syntax or selector detail, so the baseline 3 is appropriate.

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+resource ('Lock or unlock a sequencer section') and pins the exact engine function (UMovieSceneSection::SetIsLocked), which clearly separates it from the many sibling set_section_* tools that mutate other section properties.

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?

Gives explicit operational guidance: 'a locked section cannot be modified by other edit ops, so lock LAST in an edit chain.' That tells the agent when to call it relative to other edits. It does not name a specific alternative tool or a when-not-to-use case, 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