Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_anim_curve_interp_mode

DestructiveIdempotent

Set a UAnimSequence curve's EAnimAssetCurveFlags to one mode (linear, editable, metadata, drive_track, disabled), then saves the package. No key interpolation or tangents are changed.

Instructions

Replace the curve flags (the EAnimAssetCurveFlags bitmask) of an existing float or transform curve on a UAnimSequence with one flag, in an undo transaction, then save the package. Despite the name it changes no key interpolation or tangents: linear and editable both set Editable; metadata, drive_track and disabled set those flags. interp_mode is required; an unknown mode, curve or sequence is an error, and any curve_type other than transform means float. old_flags and new_flags are the bitmasks before and after; flags the curve already has are a success with applied=false, saved=false and a note, and nothing is written or saved; a failed save makes success false, with saved=false and save_error. get_anim_curve_data reads the flags.

Returns: { anim_sequence_path, curve_name, interp_mode, old_flags, new_flags, applied, saved, save_error, note? }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
curve_nameYesName of the curve
curve_typeNoCurve type to target: float (default) or transform
interp_modeYesOne of "linear|editable|metadata|drive_track|disabled"
anim_sequence_pathYesFull asset path to the UAnimSequence

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.2
    • changedInput schema / required
      Previous value: -[
-  "anim_sequence_path",
-  "curve_name"
-]New value: +[
+  "anim_sequence_path",
+  "curve_name",
+  "interp_mode"
+]
  2. First observedv1.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that it runs in an undo transaction and saves the package, maps each interp_mode value to the flag it sets (linear/editable both set Editable), and precisely describes the already-set success path (applied=false, saved=false, note) and the failed-save path (success=false, saved=false, save_error).

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?

Dense but front-loaded with the core action first, then the name caveat, then status semantics, then the return shape. Every clause carries information, though the single long run-on sentence is harder to parse than it needs to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 supplies the full return shape (anim_sequence_path, curve_name, old_flags, new_flags, applied, saved, save_error, note) and the error conditions, so an agent has everything needed to call and interpret the result.

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 schema carries the basics, but the description adds real meaning: interp_mode is required, individual mode-to-flag semantics, and that any curve_type other than transform is treated as float (default). This exceeds the baseline for fully documented parameters.

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 (replace the EAnimAssetCurveFlags bitmask of an existing float/transform curve on a UAnimSequence) and explicitly disambiguates the misleading name by noting it changes no key interpolation or tangents, which separates it from siblings like set_keyframe_interpolation and set_transform_track_interp_mode.

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?

Warns that despite the name it does not touch interpolation/tangents, which steers the agent away from misfiring on key-interpolation intent, and points to get_anim_curve_data as the read counterpart. It stops short of naming explicit when-to-use alternatives for the flag-setting itself.

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