Skip to main content
Glama

unreal_set_keyframe

Sets transform or property keyframes in Unreal Engine 5, enabling you to capture animation and property changes at specific points for editor workflows.

Instructions

Set a transform/property keyframe.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "params": "<params>"
    },
    "name": "unreal_set_keyframe"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full disclosure burden, yet it says nothing about whether this overwrites an existing keyframe, what object/sequence it applies to, or whether the operation is undoable. "Set" implies a mutation, but that is the only behavioral signal and it is inferred from a single verb.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of filler, which is good. The brevity is not conciseness so much as under-specification, so it earns an average rather than a high mark.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained. But for a mutation tool with zero annotation coverage and a completely opaque single parameter, the definition leaves too much for the agent to guess, making it only marginally complete.

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

Parameters2/5

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

Schema coverage is 0% and the single "params" property is an untyped object with no documentation, so the schema gives the agent nothing. The description's mention of "transform/property" hints at the payload's content but does not explain the required keys, value shapes, or which field selects transform versus property keyframes.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/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 ("Set ... keyframe") and narrows scope to "transform/property", which is more informative than the bare name. However, it offers no differentiation from the many sibling setters, and an agent cannot tell from this text how it relates to sequence or animation tooling.

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 guidance on when to use this tool, what prerequisites exist (e.g. an open sequence or selected object), or what alternatives a caller should consider. The caller must infer the entire usage context.

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