Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_section_completion_mode

DestructiveIdempotent

Sets how a Sequencer section handles state when no longer evaluated: keep_state, restore_state, or project_default.

Instructions

Set how a sequencer section handles state when no longer evaluated (keep_state|restore_state|project_default).

Returns: { sequence_path: string, completion_mode: string, set: bool, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
completion_modeYesOne of "keep_state", "restore_state", "project_default".
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",
-  "completion_mode"
-]New value: +[
+  "completion_mode"
+]
  2. First observedv1.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare that this mutates (readOnlyHint=false, destructiveHint=true, idempotentHint=true), so the safety profile is covered. The description earns credit by disclosing the return contract, notably a `saved` flag and optional `save_error`, which tells the agent the edit triggers an asset save that can fail — real behavioral context not present in structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, the core purpose is front-loaded, and the return-shape note is compact with no filler. Every sentence carries information an agent needs.

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?

No output schema exists, so the inline returns block is valuable and largely covers the response. With 8 parameters (7 optional) and asset-persistence side effects, it could say more about which addressing path to prefer, but the 100% schema coverage fills most gaps.

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%, so the schema already documents all 8 parameters and the completion_mode enum. The description's parenthetical listing of the three modes merely restates the schema, adding no syntax or resolution detail for how binding/track/section indices combine. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb ("Set") plus resource ("sequencer section") and the exact property being changed (state handling when no longer evaluated), which is far more precise than a tautology. It does not name or distinguish itself from adjacent sequence-section tools such as set_section_easing or set_section_active, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use, when-not-to-use, or prerequisite guidance; the only contextual hint ("see set_section_easing" for track_type) lives in the schema, not the description. The agent must infer applicability purely from the tool name.

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