Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_section_color

DestructiveIdempotent

Set the editor color tint for a specific Level Sequence section using RGB/alpha values, then save the asset so the tint persists in the Unreal Editor.

Instructions

Set the editor color tint of a sequencer section (UMovieSceneSection::SetColorTint). The tint is WITH_EDITORONLY_DATA (a no-op in cooked/no-editor-data builds); in the editor it persists on the asset.

Returns: { sequence_path: string, section_index: int, color: { r: int, g: int, b: int, a: int }, set: bool, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
aNoAlpha component 0-255 (int; default 255).
bNoBlue component 0-255 (int; default 0).
gNoGreen component 0-255 (int; default 0).
rNoRed component 0-255 (int; default 0).
track_typeNoOptional class filter (see set_section_easing).
track_indexNoIndex into the binding's tracks (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."
    • removedInput schema / required
      Removed value: -[
-  "sequence_path",
-  "binding_guid"
-]
  2. First observedv1.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=true), so the bar is lower. The description nonetheless adds real value beyond them: the WITH_EDITORONLY_DATA nature, the fact that it is a silent no-op in cooked builds, and that the tint persists on the asset in-editor. That is meaningful behavioral disclosure the annotations cannot convey.

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 front-load the purpose, then the caveat, followed by the return shape. Every clause carries weight: the native symbol, the editor-only behavior, and the persistence outcome. No filler.

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 0-required-parameter, 11-param tool with no output schema, the description supplies the return shape and the critical editor-only limitation, which is exactly the kind of context an agent needs before invoking. The only minor gap is the absence of guidance on resolving the binding/section targets versus sibling tools, but overall it is complete for its complexity.

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 11 parameters, including the r/g/b/a channels, alias fields, and binding/section indices. The description adds no parameter-level meaning beyond what the schema provides, so the baseline of 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 and resource ('Set the editor color tint of a sequencer section') and anchors it to the native API UMovieSceneSection::SetColorTint. This cleanly separates it from sequencer siblings like set_section_easing, set_section_blend_type, and set_section_active, which all operate on the same section but for different properties.

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 editor-only caveat ('no-op in cooked/no-editor-data builds') tells the agent when the call is meaningful, which is genuine context. However, there is no explicit guidance about when to prefer this over sibling section-mutators or any prerequisites for resolving the binding/section. Usage is implied rather than stated.

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