Skip to main content
Glama

unreal_add_sequence_track

Adds a new track to an Unreal Engine sequence, enabling organized editing of animation, audio, or other timeline content.

Instructions

Add a sequence track.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/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 behavioral burden and discloses nothing: not whether the change is persistent, what permissions or open-editor state are required, what happens on failure, or whether adding a track mutates an existing sequence asset. 'Add' implies mutation but no consequences or reversibility are described.

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 single sentence is free of padding, but conciseness here reflects under-specification rather than efficiency. There is no front-loaded context, no structure, and nothing for the agent to act on beyond the name.

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

Completeness2/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 needn't be explained, but for a mutation tool with zero annotations and a completely opaque 'params' object the definition is far too thin. It omits the information an agent needs to call it correctly or to know it succeeded.

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?

There is one required parameter named 'params' whose schema is an untyped object with no properties and 0% description coverage. The description adds no information about what belongs in that object (track type, binding, index, sequence reference), leaving the agent unable to construct a valid call.

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 is the tool name with underscores removed: 'Add a sequence track.' It names a verb and a resource but adds no distinguishing detail versus siblings such as unreal_add_sequence_section or unreal_create_level_sequence, so an agent cannot tell which sequence-track-like operation this is from the text alone.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. The agent receives no signal about how this differs from unreal_add_sequence_section or when a track should be added via this tool versus through sequence creation.

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