Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_section_info

Read-onlyIdempotent

Get detailed sequencer section properties: range, easing, completion mode, blend type, lock state. Inspect animation timing and behavior in Unreal Engine sequences.

Instructions

Get detailed info about a sequencer section: range, easing, completion mode, blend type, lock/infinite state.

Returns: { sequence_path: string, section_index: int, start_frame: int, end_frame: int, ease_in_frames: int, ease_out_frames: int, manual_ease_in: bool, manual_ease_out: bool, completion_mode: string, blend_type: string, blend_type_valid: bool, is_locked: bool, is_active: bool, is_attach_section: bool, attach_rules: object? }

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 inspect.
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

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, so the safety profile is covered. The description adds real value beyond that by enumerating the full returned payload (easing frames, completion_mode, blend_type, is_locked, is_active, attach_rules), which matters because no output schema exists.

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 with the purpose front-loaded and the return shape immediately following. The return-field list is long but earns its place given the absence of an output schema.

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 zero-required-param read tool with full schema coverage, the description supplies what the schema cannot: the shape of the response object. Only the absence of any selection/usage context keeps it from a 5.

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 seven parameters including defaults and aliases. The description adds no parameter-level meaning beyond that, making the baseline 3 appropriate.

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?

The description states a specific verb and resource ('Get detailed info about a sequencer section') and enumerates the properties returned, which distinguishes it from the surrounding set_section_* mutators. It does not explicitly name or differentiate itself from sibling readers such as get_sequence_tracks or get_binding_tracks, 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 guidance, no prerequisites, and no named alternative. The only routing hint ('see set_section_easing') lives in the schema's track_type description, not in the tool description itself. Usage is inferable from the name but not 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