Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_channel_keyframes

Read-onlyIdempotent

Read every keyframe on a channel of a binding's section in a Level Sequence, returning frame, time, value, and interpolation data. Use to inspect animation curves without modifying the asset.

Instructions

Read every keyframe on one channel of a binding's section (resolved like set_section_easing). Pure reader (no transaction/save). channel_type selects which channel proxy view to index: "double" (transform loc/rot/scale, default), "float" (property/color), "bool" (visibility). Bool keys omit interp/tangent fields.

Returns: { sequence_path: string, channel_index: int, channel_type: string, key_count: int, keyframes: [{ index: int, frame: int, time_seconds: number, value: number|bool, interp_mode: string, tangent_mode: string, arrive_tangent: number, leave_tangent: number }] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_typeNoOptional class filter (see set_section_easing) selecting the track on the binding.
track_indexNoIndex into the binding's tracks (default 0; used when track_type omitted).
binding_guidNoGUID of the binding whose section to read.
channel_typeNoChannel value kind: "double" (default) | "float" | "bool".
channel_indexNoIndex of the channel within its proxy view (default 0).
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.1/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive. The description adds genuinely new behavior: it is a 'pure reader (no transaction/save)', channel_type determines which proxy view is indexed, and bool keys omit interp/tangent fields. These are meaningful details beyond the annotations.

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?

Front-loads the core action, then lists channel_type semantics and a return shape in a logical order with little waste. The embedded Returns block is dense but justified given there is no 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?

With no output schema, the description compensates by describing the return structure and jittering out the channel_type resolution rule. It is nearly complete for a 9-parameter read tool, though it could note binding/GUID resolution requirements more explicitly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description enriches it by mapping channel_type values to concrete meanings ('double' = transform loc/rot/scale, 'float' = property/color, 'bool' = visibility) and noting bool keys drop certain fields — detail the schema's terse 'Channel value kind' line lacks.

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: 'Read every keyframe on one channel of a binding's section.' It distinguishes itself from sibling readers like get_curve_keys or get_binding_tracks by scoping to a single channel proxy view, and it cross-references set_section_easing for the resolution semantics an agent needs.

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 clarifies its read-only nature and how channel_type selects the proxy view, which helps correct invocation. It does not, however, state when to choose this tool over adjacent keyframe readers (e.g., get_curve_keys, get_anim_curve_data) or any preconditions, so usage is only implied.

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