Skip to main content
Glama
Sign In
o3de-mcp

o3de-mcp

by nickschuetz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_sequence

Creates a new Track View cinematic sequence in the current O3DE level as a Sequence Component entity; add a Director node before adding other nodes.

Instructions

Create a new Track View cinematic sequence in the current level.

Creates a modern Sequence Component sequence (on its own entity). A new sequence has no nodes; add a Director node with add_sequence_node before adding other nodes. An existing name is reported as an error.

Args: name: Sequence name.

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": {
      "name": "<name>"
    },
    "name": "create_sequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses the initial state (no nodes) and the error behavior on duplicate names, but says nothing about persistence, undo behavior, permissions, or whether the current level must be loaded/saved.

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

Conciseness4/5

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

Purpose is front-loaded in the first sentence, followed by the node-workflow caveat and the duplicate-name constraint. Efficient overall, though the 'Args' block adds little and is somewhat redundant.

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

Completeness4/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. For a simple single-parameter creation tool, the description covers creation, initial state, follow-up call, and the duplicate-name error – the main omission is any note on persistence or level context.

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

Parameters3/5

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

Schema description coverage is 0% for the single 'name' parameter, and the 'Args' block only restates 'Sequence name'. The uniqueness constraint mentioned in the body ('An existing name is reported as an error') does add real semantic value about the parameter.

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

Purpose5/5

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

States a specific verb ('Create') and resource ('Track View cinematic sequence'), scoped to the current level, and notes it produces a Sequence Component on its own entity. This clearly distinguishes it from siblings like list_sequences, get_sequence, and delete_sequence.

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

Usage Guidelines4/5

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

Gives explicit workflow guidance: a new sequence has no nodes, so add a Director node with add_sequence_node before adding others. It names the follow-up tool and the condition for using it, though it does not state when a caller should prefer creating a new sequence over reusing an existing one.

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