Skip to main content
Glama

create_sound_source_bus

Destructive

Create or load a USoundSourceBus asset, write its channel, duration, and audio bus routing fields, then save it. All inputs are validated before any change.

Instructions

Creates a USoundSourceBus asset at package_path/name, or loads the one already there, writes its routing fields and saves it; another asset class at the path is an error. source_bus_channels and duration, when omitted, take the defaults (Stereo, 1.0 s) on a new asset and keep their value on an existing one, whose fields the given values overwrite. Every value is validated before any asset is created or loaded, so an invalid one leaves nothing behind. audio_bus_path, when given, must load as a UAudioBus and becomes the bus whose audio this source bus plays; when omitted that field is left as is. Edit later with set_sound_source_bus_audio_bus or set_sound_source_bus_send_info; read with get_sound_source_bus.

Returns: { name: string, package_path: string, asset_path: string, asset_class: string, source_bus_channels: string, duration: float, audio_bus_path: string, audio_bus_class: string, applied_channels: bool, applied_duration: bool (each true when this call wrote the field: given, or the default on a new asset), applied_audio_bus: bool, created: bool, already_exists: bool, saved: bool, save_error?: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the new Sound Source Bus asset
durationNoDuration in seconds, at least 0 (0.0 means indefinite); a negative value is an error. Default 1.0 on a new asset only.
package_pathNoTarget content path, defaults to /Game/Audio
audio_bus_pathNoOptional full content path of a UAudioBus to assign as the AudioBus return.
source_bus_channelsNoESourceBusChannels: 'Mono' | 'Stereo' (default). USoundSourceBus inherits only Mono/Stereo. The default applies to a new asset only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.2
    • changedInput schema / properties / duration / description
      Previous value: -"Duration in seconds (ClampMin=0.0; 0.0 means indefinite). Default 1.0."New value: +"Duration in seconds, at least 0 (0.0 means indefinite); a negative value is an error. Default 1.0 on a new asset only."
    • changedInput schema / properties / source_bus_channels / description
      Previous value: -"ESourceBusChannels: 'Mono' | 'Stereo' (default). USoundSourceBus inherits only Mono/Stereo."New value: +"ESourceBusChannels: 'Mono' | 'Stereo' (default). USoundSourceBus inherits only Mono/Stereo. The default applies to a new asset only."
  2. First observedv1.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=false, and the description earns its keep by disclosing behavior beyond them: values are validated before anything is created/loaded so an invalid value 'leaves nothing behind' (atomicity), defaults apply only on a new asset, and existing fields are overwritten. It also explains what audio_bus_path does and when it is left as is.

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?

Front-loaded with the primary action ('Creates ... or loads the one already there'), then constraints, then alternatives. It is dense and one long paragraph, but every clause carries information (atomicity, defaults, return shape); nothing is filler, though it could be broken up slightly for scanability.

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?

There is no output schema, and the description compensates by fully enumerating the return fields (asset_path, applied_channels/duration/audio_bus flags, created, already_exists, saved, save_error). Combined with the atomicity and default-scope notes, an agent has everything needed to call and interpret the result.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description goes further by explaining that omitted source_bus_channels/duration take defaults on a new asset but keep their values on an existing one, and that audio_bus_path must resolve to a UAudioBus and sets the return bus. This adds semantics (default-scope and validation constraints) that the schema does not fully convey.

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 ('Creates a USoundSourceBus asset at package_path/name') and precisely describes the upsert behavior (loads the existing one). It explicitly names the sibling tools it does not replace (set_sound_source_bus_audio_bus, set_sound_source_bus_send_info, get_sound_source_bus), so an agent can distinguish it without opening a schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: create here, then 'Edit later with set_sound_source_bus_audio_bus or set_sound_source_bus_send_info; read with get_sound_source_bus.' It also states the create-or-load semantics and the error condition (another asset class at the path), which tells the agent when this call is appropriate.

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