Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

create_control_bus

Create or load a USoundControlBus asset at a target package path and save it, returning bus path, default value, and creation status. Ensures a bus exists before setting runtime values.

Instructions

Creates a USoundControlBus asset at package_path/bus_name, or loads the one already there, and saves it. initial_value is only echoed back as value, never written to the bus; push a runtime value with set_control_bus_value. Returns bus_path, default_value, created, already_existed, saved.

Returns: { bus_path, bus_name, value, default_value, created, already_existed, saved }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bus_nameYesName of the control bus (e.g. "Bus_Volume")
package_pathNoTarget content package path where the asset is created (default /Game/MCP)
initial_valueNoNumber echoed back as value in the reply; it is not stored on the bus (default 1.0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / initial_value / description
      Previous value: -"Initial bus value echoed back (default 1.0)"New value: +"Number echoed back as value in the reply; it is not stored on the bus (default 1.0)"
  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?

Discloses a genuinely non-obvious behavior — that initial_value is echoed as value but never written to the bus — plus the load-or-create semantics and that the asset is saved. Annotations only cover the safety profile (write, non-destructive, local), so this description carries real added behavioral value.

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

Conciseness3/5

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

The scoping and initial_value caveats are front-loaded well, but the return list is stated twice and the two statements are inconsistent — the first omits bus_name and value, the second includes them — which is redundant and slightly confusing.

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?

For a write tool with no output schema, the description covers the side effects (create or load, save), the parameters' real behavior, the return fields, and the correct alternative for runtime values. Nothing an agent needs in order to call it correctly is missing.

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 would be 3. The description adds meaning beyond the schema by clarifying the package_path/bus_name composition and reinforcing the echo-only semantics of initial_value along with the correct tool for setting a live value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource (creates a USoundControlBus asset at package_path/bus_name, or loads an existing one and saves it), which is far more precise than the bare tool name. It does not explicitly distinguish itself from close siblings like create_audio_bus or create_sound_source_bus, so it stops short of a 5.

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

Usage Guidelines4/5

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

Gives a clear conditional: initial_value is only echoed back and is never stored, and runtime values should be pushed with set_control_bus_value instead. That names an alternative tool and the condition selecting it. It doesn't cover when to prefer this over the other bus-creation siblings, so not a full 5.

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