o3de-mcp

by nickschuetz

Overview Schema Source Related Servers Discussions Admin

Python

Local

set_parent

Assign a new parent to an entity to reorganize the O3DE hierarchy. Specify entity and parent IDs to reparent.

Instructions

Set the parent of an entity (reparent in the hierarchy).

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>",
      "parent_id": "<parent_id>"
    },
    "name": "set_parent"
  }
}

Input Schema

Name	Required	Description	Default
`entity_id`	Yes
`parent_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.5/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the parent is changed, but does not mention side effects such as child behavior, whether the previous parent relationship is removed, or whether the operation can fail.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no wasted words. It immediately communicates the operation and the domain in which it operates.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with only two required parameters, and an output schema exists, so return values need not be explained. Still, the description omits behavioral details that would help an agent understand the full impact of reparenting, such as whether the parent must exist or what happens to existing children.

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%, so the description must compensate. The natural language 'Set the parent of an entity' implies entity_id is the child and parent_id is the new parent, and the parenthetical adds the concept of reparenting. However, it does not define the parameters explicitly or clarify edge cases like detaching from a parent.

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?

The description clearly states a specific action and resource: 'Set the parent of an entity' with the clarifying parenthetical '(reparent in the hierarchy)'. This uniquely distinguishes it from sibling tools like set_transform or set_component_property, since 'parent' is a different hierarchy concept.

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 phrase 'reparent in the hierarchy' implies the tool is used when changing an entity's parent-child relationship. However, it does not explicitly state when to choose this over alternatives, nor does it mention any exclusions or prerequisites.

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

Deploy Server