Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

create_sound_concurrency

Create or load a sound concurrency asset in Unreal Engine to limit how many grouped sounds play simultaneously, optionally setting MaxCount and saving it.

Instructions

Create a USoundConcurrency asset at package_path/name, or load the one already there, optionally set MaxCount, and save it. Returns max_count read back, created, already_exists and saved; set_sound_concurrency_properties edits the other concurrency settings.

Returns: { name: string, package_path: string, asset_path: string, asset_class: string, max_count: int, applied_max_count: bool, created: bool, already_exists: bool, saved: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the new Sound Concurrency asset
max_countNoMost sounds of this group that play at once (MaxCount); values below 1 become 1 and fractions are truncated. Unchanged when omitted.
package_pathNoTarget content path, defaults to /Game/Audio

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / max_count / description
      Previous value: -"Optional MaxCount on FSoundConcurrencySettings, clamped to >= 1"New value: +"Most sounds of this group that play at once (MaxCount); values below 1 become 1 and fractions are truncated. Unchanged when omitted."
  2. First observedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the safety profile (not read-only, not destructive). The description adds genuinely useful behavior beyond that: it is an upsert (loads an existing asset if present), it saves the asset, and it reports created/already_exists/saved flags. It does not mention failure modes or whether an existing asset is overwritten, which keeps it from a 5.

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 core action and sibling pointer in the first sentence; the explicit return list is verbose but earns its place since no output schema exists. Minor repetition between the summary sentence and the detailed Returns block.

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?

With no output schema, the description helpfully enumerates the return fields, and it covers purpose, alternative, and upsert behavior across an already-rich schema and annotation set. Missing only edge-case behavior (overwrite semantics, failure handling).

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 parameters are already documented. The description adds the path-composition semantics of 'package_path/name' but largely restates MaxCount's optionality already covered in the schema, so 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?

States a specific verb and resource (create a USoundConcurrency asset), explains the upsert behavior (create or load existing), and names the sibling that handles the remaining fields (set_sound_concurrency_properties). An agent can distinguish this from the many other audio-asset creators 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 Guidelines4/5

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

It clearly routes the agent: MaxCount goes here, other concurrency settings go to set_sound_concurrency_properties, and it explains the create-or-load-existing condition. It lacks an explicit 'when not to use' or prerequisite (e.g., permissions, existing asset conflicts), but the context is unambiguous.

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