Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_anim_curve_keys

DestructiveIdempotent

Replace every key of an existing float curve on a UAnimSequence with [time, value] pairs as linear keys, then save the package and return the key count.

Instructions

Replace every key of an existing float curve on a UAnimSequence with the given [time, value] pairs as linear keys with auto tangents, through its data controller in an undo transaction, then save the package; num_keys is read back. The curve must exist (add_anim_float_curve first) and keys needs at least one valid pair. A transform curve is refused, since its keys are transforms, not [time, value] pairs: rekey it with add_anim_transform_curve. Any other curve_type is an error, and so is a rekey the data controller rejects, with nothing saved. A curve that already holds exactly those keys is 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.

Returns: { anim_sequence_path, curve_name, curve_type, num_keys, applied, saved, save_error, note? }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keysNoJSON array of [time, value] pairs, time in seconds, at least one; entries that are not such a pair are skipped, and tangents or interpolation cannot be given.
curve_nameYesName of the float curve (e.g. "MyCurve")
curve_typeNoCurve type to target: float (default) or transform; transform is refused with an error pointing at add_anim_transform_curve.
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 / properties / curve_type / description
      Previous value: -"Curve type to target: float (default) or transform"New value: +"Curve type to target: float (default) or transform; transform is refused with an error pointing at add_anim_transform_curve."
  2. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / keys / description
      Previous value: -"JSON array of {time, value, arrive_tangent?, leave_tangent?, interp_mode?} objects"New value: +"JSON array of [time, value] pairs, time in seconds, at least one; entries that are not such a pair are skipped, and tangents or interpolation cannot be given."
  3. First observedv1.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations (destructive, idempotent, non-read-only) by disclosing that the change runs through the data controller in an undo transaction and then saves the package, that a no-op rekey returns applied=false/saved=false with nothing written, and that a failed save yields success false with save_error. This is exactly the behavioral context annotations cannot carry.

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?

The core mutation and its constraints are front-loaded, and the trailing Returns line is useful given there is no output schema. The single dense paragraph is slightly heavy but every clause carries an actionable constraint, so little is wasted.

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?

For a destructive, idempotent mutation with no output schema, the description covers prerequisites, refusal cases, idempotent no-op semantics, save failure behavior, and enumerates the return fields. Nothing an agent needs to call it correctly is missing.

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 already 100%, so the baseline is 3, but the description adds real meaning: keys are linear with auto tangents, tangents/interpolation cannot be specified, non-pair entries are skipped, and curve_type=transform is refused with a pointer to the alternative. It slightly exceeds the schema rather than merely restating it.

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 and resource: replacing every key of an existing float curve on a UAnimSequence with [time, value] pairs as linear keys. It explicitly distinguishes itself from the sibling operations add_anim_float_curve (creation prerequisite) and add_anim_transform_curve (the alternative for transform curves).

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

Usage Guidelines5/5

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

Gives explicit preconditions (the curve must already exist, create it with add_anim_float_curve first) and explicit exclusions/routing (transform curves are refused; use add_anim_transform_curve instead). The agent knows when to use this and when to pick a sibling.

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