Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_binding_channel_keyframe_interp

DestructiveIdempotent

Edit one keyframe on a binding’s section channel by setting its interpolation, tangent mode, arrive/leave tangents, or value for animation control.

Instructions

Set the interpolation mode, tangent mode, tangents and/or value of one keyframe on a binding's section channel (resolved like set_section_easing). Like set_keyframe_interpolation but for per-binding channels: transform "double" (default) or property "float". Bool channels have no interp/tangent and are rejected. Idempotent (writing the same fields = same state).

Returns: { sequence_path: string, channel_index: int, channel_type: string, frame: int, key_index: int, value: number, interp_mode: string, tangent_mode: string, arrive_tangent: number, leave_tangent: number, set: bool, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frameNoFrame of the key to edit (resolved via FindKey; provide index OR frame).
indexNoIndex of the key to edit (mutually exclusive with frame).
valueNoOptional new key value (leaves unchanged if omitted).
toleranceNoOptional FindKey frame tolerance when locating by frame (default 0).
track_typeNoOptional class filter (see set_section_easing) selecting the track on the binding.
interp_modeNoOptional interpolation: "Cubic" | "Linear" | "Constant" (default leaves unchanged).
track_indexNoIndex into the binding's tracks (default 0; used when track_type omitted).
binding_guidNoGUID of the binding whose section to edit.
channel_typeNoChannel value kind: "double" (default) | "float". ("bool" is rejected -- no interp/tangent.)
tangent_modeNoOptional tangent mode (Cubic only): "Auto" | "User" | "Break" (default leaves unchanged).
channel_indexNoIndex of the channel within its proxy view (default 0).
leave_tangentNoOptional leave tangent value (Cubic).
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.
arrive_tangentNoOptional arrive tangent value (Cubic).
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 declare readOnly=false, idempotent=true, destructive=true, and the description reinforces idempotency ('writing the same fields = same state'). It adds real behavioral context beyond the annotations: bool-channel rejection, Cubic-only tangent constraints, and 'default leaves unchanged' semantics for optional fields. It does not spell out what existing keyframe data gets overwritten given destructiveHint=true, so not a 5.

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-loaded with the action and its sibling relationship, then constraints, then a compact Returns block. Mostly earns its space, though the long enumerated Returns object is heavy relative to the prose and could arguably be trimmed.

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 17-parameter mutation with no output schema, the description supplies the missing return shape and the key constraints an agent needs (channel types, rejection cases, idempotency). It lacks detail on permission/auth needs and precisely which fields are overwritten, but is otherwise complete for correct invocation.

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 17 parameters including defaults and enum values. The description only adds the transform-double/property-float channel distinction and the Cubic-only tangent note, which are marginal additions over the schema. 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 precise verb+resource ('Set the interpolation mode, tangent mode, tangents and/or value of one keyframe') and explicitly distinguishes itself from siblings: 'resolved like set_section_easing' and 'Like set_keyframe_interpolation but for per-binding channels'. An agent can identify the tool's niche without opening the schema.

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

Usage Guidelines4/5

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

Clearly frames when this tool applies (per-binding channels vs the general set_keyframe_interpolation) and states a key exclusion: bool channels are rejected because they have no interp/tangent. It also gives the channel-type selection rule ('transform double default, property float'). No explicit when-not routing beyond the sibling comparison, so not a full 5.

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