Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_sound_class_parent

DestructiveIdempotent

Re-parent a USoundClass by assigning a new parent and saving both packages. Updates ParentClass and ChildClasses links in Unreal Engine.

Instructions

Make one USoundClass the child of another, wiring ParentClass and ChildClasses, and save both packages. A previous parent loses the child in memory but is not saved; only self-parenting is refused, not cycles. Returns child_count, saved_parent and saved_child, succeeding even when a save fails.

Returns: { child: string, parent: string, child_path: string, parent_path: string, child_count: int, saved_parent: bool, saved_child: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
child_sound_class_pathYesAsset path of the USoundClass to re-parent, e.g. "/Game/Audio/SC_Footsteps.SC_Footsteps".
parent_sound_class_pathYesAsset path of the USoundClass that becomes its parent, e.g. "/Game/Audio/SC_SFX.SC_SFX".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • changedInput schema / properties / child_sound_class_path / description
      Previous value: -"Full content path of the child USoundClass"New value: +"Asset path of the USoundClass to re-parent, e.g. \"/Game/Audio/SC_Footsteps.SC_Footsteps\"."
    • changedInput schema / properties / parent_sound_class_path / description
      Previous value: -"Full content path of the parent USoundClass"New value: +"Asset path of the USoundClass that becomes its parent, e.g. \"/Game/Audio/SC_SFX.SC_SFX\"."
  2. First observedv1.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses rich behavioral traits: the previous parent loses the child in memory but is not saved, only self-parenting is refused while cycles are permitted, both packages are saved, and the call succeeds even when a save fails. This is exactly the additional context annotations cannot express.

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 main action is front-loaded, followed by the key edge-case behavior and the return shape. Every sentence earns its place, and since no output schema exists, spelling out the return fields is justified rather than redundant.

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

Completeness5/5

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

With no output schema, the description compensates by naming the returned fields (child_count, saved_parent, saved_child), and it covers persistence semantics, edge-case validation, and failure tolerance. An agent has everything needed to call and interpret the tool correctly.

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 100%, so the schema already documents both required path parameters with examples. The description restates the ParentClass/ChildClasses wiring but adds no path syntax or format meaning beyond the schema, so the baseline 3 applies.

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 states a specific verb+resource (re-parent a USoundClass, making one the child of another) and identifies its role among siblings like create_sound_class, set_sound_class_properties, and get_sound_class_hierarchy. An agent can distinguish this tool immediately 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 implies usage (re-parenting operation) but never explicitly states when to use this versus alternatives such as set_sound_class_properties. It does clarify notable constraints (cycles allowed, self-parenting refused), which helps an agent decide plausibility, but gives no forward when-to-use routing.

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