Skip to main content
Glama

unreal_get_level_sequences

Lists Level Sequences in an Unreal Engine 5 project so AI clients can inspect and select sequences for editing workflows.

Instructions

List Level Sequences.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether the call is read-only, what the result set is scoped to, whether pagination or filtering applies, or what happens on an empty level. Two words cannot convey behavior for an editor-facing query tool.

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?

It is certainly short and front-loaded, but this is under-specification rather than conciseness: a two-word sentence with no scope, no qualifiers, and no structure carrying any operational detail. Nothing here would be cut, because there is nothing to cut.

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-value explanation is not required, but the single required parameter is completely opaque and the description does nothing to resolve it. For a tool whose only input is an undocumented "params" blob, the description leaves the caller without enough information to invoke it confidently.

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?

One required parameter exists with 0% schema description coverage and is typed only as an untyped "Params" object with no declared properties, so neither schema nor description explains what to pass. The description offers no compensation whatsoever for this gap.

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?

"List Level Sequences" gives a verb (list/enumerate) plus the resource, which distinguishes it from siblings like unreal_create_level_sequence or unreal_get_current_level. However, it adds nothing beyond a rewording of the tool name and gives no scope, so an agent still cannot tell exactly what a "Level Sequence" collection contains or how it differs from other list-style siblings.

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 at all: nothing says whether this lists all sequences in the project, in the current level, or in a folder, nor when to prefer it over unreal_get_current_level or unreal_analyze_level_composition. The agent must infer usage purely 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