o3de-mcp

by nickschuetz

Overview Schema Source Related Servers Discussions Admin

Python

Local

delete_entity

Remove an entity from the current O3DE level using its entity ID; missing entities and the root entity are refused.

Instructions

Delete an entity from the current O3DE level.

Tries the gem's native delete_entity request first (gem 0.5.0 or later, works in secure mode) and returns its JSON verbatim: {"deleted": <id>}. A missing entity or the level's root entity is refused by the gem and returned as an error. Older gems and the legacy transport fall back to editor Python, which prints Deleted entity [<id>].

Args: entity_id: The entity ID to delete.

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

Input Schema

Name	Required	Description	Default
`entity_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Sep 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the two execution paths, the verbatim JSON return shape, and the error cases (missing entity and root entity are refused). It omits whether the deletion is reversible/undoable and any permission requirements, which are material for a destructive operation.

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 escalation detail and a compact Args block. It is slightly verbose on output formatting, but nearly every sentence carries operational information.

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, yet the description still usefully previews the return shapes for both paths. Combined with the error-case coverage it is nearly complete for a one-parameter destructive tool, though it should flag irreversibility/undo availability given the sibling undo tool.

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 coverage is 0% and the only argument is glossed as 'the entity ID to delete', which mostly restates the parameter name. It does add some semantics by noting that missing IDs and the root entity ID are rejected, giving a hint about valid values.

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 ('Delete') and resource ('an entity from the current O3DE level'), which is unambiguous against siblings like create_entity, duplicate_entity, and remove_component. An agent can identify exactly what the tool does without opening 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?

The description explains the execution paths and their preconditions (gem 0.5.0+, secure mode; older gems fall back to editor Python), which is useful operational context. However, it never states when to prefer this over an alternative or what prerequisites (e.g., level loaded) must hold before calling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server