Skip to main content
Glama
Sign In
o3de-mcp

o3de-mcp

by nickschuetz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create_level

Create a new level in the current O3DE project and open it in the editor, choosing a level name and optional template prefab.

Instructions

Create a new level in the current O3DE project and open it in the editor.

Args: name: Level name (alphanumeric, hyphens or underscores, starting with a letter). The level is written to <project>/Levels/<name>/. template: Level template prefab, as a path relative to an asset scan folder. Defaults to the editor's own New Level default, Prefabs/Default_Level.prefab (camera, sun, grid). Pass an empty string for a bare level with no entities.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
templateNoPrefabs/Default_Level.prefab

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • addedInput schema / properties / template
      Added value: +{
+  "default": "Prefabs/Default_Level.prefab",
+  "title": "Template",
+  "type": "string"
+}
  2. First observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations, so the description carries the full burden, and it does disclose real behavior: where the level is written (<project>/Levels/<name>/), what the default template contains (camera, sun, grid), and that an empty template string yields a bare level with no entities. It omits what happens if a level of that name already exists and any error/permission behavior, which keeps it from a 5.

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?

The primary action is front-loaded in the first sentence, and the per-argument notes each earn their place by adding constraints and semantics not present in the schema. Slightly verbose but no wasted sentences.

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?

For a two-parameter mutation tool with an output schema, the description covers naming rules, destination, template default, and the empty-string edge case, so an agent can call it confidently. The remaining gap is collision/overwrite behavior when the target name already exists.

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

Parameters5/5

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

Schema coverage is 0%, so the description must compensate, and it does: it gives the naming constraint (alphanumeric, hyphens or underscores, starting with a letter), the destination path for name, and for template the resolution base (relative to an asset scan folder), the default value, and the special empty-string semantics.

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 and resource ('Create a new level in the current O3DE project') plus a secondary effect ('open it in the editor'). This clearly separates it from sibling load_level and save_level without needing the schema.

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

Usage Guidelines3/5

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

Usage context is implied by 'current O3DE project' and the editor-opening behavior, and the template arg hints at the create workflow. However, it never states when to use this versus load_level or list_levels, nor any prerequisites or state requirements.

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