Skip to main content
Glama

unreal_set_sequence_duration

Set the duration of an Unreal Engine 5 sequence to control playback length and timing for editor workflows.

Instructions

Set sequence duration.

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_sequence_duration"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full disclosure burden for a mutation operation, and it discloses nothing: not what gets altered, whether existing keyframes are retimed or clipped, whether the sequence must already exist, or what permissions/state are required. This is effectively an unannotated write tool with zero behavioral context.

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

Conciseness2/5

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

The sentence is short and front-loaded, but its brevity comes from under-specification rather than economy; there is no structure or detail to justify the near-empty text.

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

Completeness1/5

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

For a mutating tool with an untyped nested params object and no annotations, the definition is far too thin. An output schema exists, which excuses not describing return values, but nothing else an agent needs in order to call this correctly is present.

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

Parameters1/5

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

The single required parameter is an opaque "params" object with 0% schema description coverage and no properties described anywhere. The description adds no meaning about what goes inside it (duration value, units, sequence identifier), so the caller cannot construct a valid invocation from the definition alone.

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

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name verbatim ("Set sequence duration") without identifying which kind of sequence (level sequence vs. animation sequence, both of which appear as siblings) or what the duration applies to. A specific verb is present, but the resource and scope stay as vague as the name.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no mention of prerequisites, and no reference to alternatives such as unreal_set_animation_sequence or unreal_add_sequence_section. The agent is left to infer everything from the name.

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