Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_section_active

DestructiveIdempotent

Control whether a sequencer section is evaluated or muted. Returns the actual state, accounting for locked sections that ignore changes.

Instructions

Toggle whether a sequencer section is active (evaluated) or muted. Maps to UMovieSceneSection::SetIsActive; reports the actual is_active read back (SetIsActive is a no-op on a LOCKED section).

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activeYesDesired active state (true = evaluated, false = muted).
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",
-  "active"
-]New value: +[
+  "active"
+]
  2. First observedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=true, so the safety profile is partially covered. The description adds genuinely useful behavior beyond that: SetIsActive is a no-op on a LOCKED section, and the return reports the actual is_active read back along with a saved flag and optional save_error, telling the agent that persistence is attempted and that the requested state may not take effect.

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 dense sentences plus a compact return-shape line, with the core purpose front-loaded and no filler. The return-shape enumeration is justified because no output schema exists, though it is slightly list-like.

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 compensates by naming the returned fields and flagging the locked-section no-op, and the schema fully documents the 8 parameters. It stops short of explaining the destructiveHint=true implication, but overall an agent has what it needs to call it correctly.

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 (including aliases and defaults) are documented in the schema itself; the description adds no syntax, format, or resolution detail for parameters. Baseline 3 is appropriate when the schema carries the parameter burden.

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 (toggle), resource (sequencer section), and effect (active/evaluated vs muted), plus names the underlying API UMovieSceneSection::SetIsActive. Among the many set_section_* siblings (set_section_locked, set_section_easing, set_section_color, etc.) an agent can immediately tell this one mutates the section's active state.

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

Usage Guidelines3/5

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

The description makes the intent of the operation clear (mute/unmute a section) but offers no explicit when-to-use, when-not, or named alternatives among the sibling set_section_* tools. Usage is only implied by the verb and the note about locked sections.

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