Skip to main content
Glama

unreal_create_level_sequence

Create a Level Sequence in Unreal Engine to organize actors and timing for cinematics or gameplay events.

Instructions

Create a Level Sequence.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.5/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 burden of behavioral disclosure, yet it says nothing about whether the sequence is persisted to disk, whether it requires an open level, what permissions or editor state are needed, or whether the operation is reversible. For a mutation tool with zero annotation coverage this is a critical gap.

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 short but that is under-specification, not conciseness; there is no structure or front-loaded detail because there is essentially no content. Every sentence that would earn a place here is missing.

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?

Although an output schema exists so return values need not be explained, the definition leaves the required 'params' object, the tool's execution context, and its behavioral effects entirely undocumented. Given the complexity of the Unreal sequence workflow implied by the sibling tools, this definition is completely inadequate.

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, 'params', whose schema gives no description and 0% coverage, and the description adds no meaning whatsoever about its expected shape or contents. An agent has no way to know what to put into this object.

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?

"Create a Level Sequence" restates the tool name (unreal_create_level_sequence) almost word for word, giving no verb or scope beyond what the identifier already conveys. It does not distinguish the tool from siblings such as unreal_create_level or unreal_get_level_sequences, so an agent gains nothing it could not infer from the name 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 prerequisite information, and no mention of any alternative for sequence creation or inspection. The agent must guess whether this tool creates an empty asset, an in-level sequence, or something requiring an existing level 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