Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_sound_source_bus_send_level_curve

DestructiveIdempotent

Merges a float curve into a USoundSourceBus send's CustomSendLevelCurve and saves it, returning the applied curve. The send must use the CustomCurve control method.

Instructions

Merge a FRuntimeFloatCurve JSON into BusSends[send_index].CustomSendLevelCurve of a USoundSourceBus asset (BusSends grows with default entries past its end) and save it; success requires the save. Returns the curve read back. The curve only takes effect when that send uses the CustomCurve control method: see set_sound_source_bus_send_info.

Returns: { ssb_path: string, send_index: int, bus_sends_count: int, distance_curve: object, applied_keys: [string], saved: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ssb_pathYesFull content path of the target USoundSourceBus (USoundBase.BusSends is the target array).
send_indexYes0-based index into BusSends; the entry is mutated in place. Resized/extended with default-constructed entries if out of range.
distance_curveYesFRuntimeFloatCurve fields by their UPROPERTY names, e.g. {"EditorCurveData": {"Keys": [{"Time": 0.0, "Value": 1.0}, {"Time": 1.0, "Value": 0.0}]}}; Time 0-1 maps to MinSendDistance-MaxSendDistance and Keys replaces the key list. Fields left out keep their current values; unknown keys are ignored without error.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / distance_curve / description
      Previous value: -"Object representing FRuntimeFloatCurve authoring data. Usable shape: { 'editor_curve_data': { 'float_curve': { 'keys': [ { 'time': float, 'value': float }, ... ] } } }. Absent keys are left at the struct default."New value: +"FRuntimeFloatCurve fields by their UPROPERTY names, e.g. {\"EditorCurveData\": {\"Keys\": [{\"Time\": 0.0, \"Value\": 1.0}, {\"Time\": 1.0, \"Value\": 0.0}]}}; Time 0-1 maps to MinSendDistance-MaxSendDistance and Keys replaces the key list. Fields left out keep their current values; unknown keys are ignored without error."
  2. First observedv1.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true), the description discloses that BusSends grows with default-constructed entries past its end, that the operation is a merge where omitted fields are preserved, and that success requires the save. This meaningfully clarifies what is mutated and what the write guarantee 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-loads the core action and target, then packs the save requirement, effect precondition, and return shape into dense but useful sentences. Slightly compressed, but every clause carries information.

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 present, the description supplies the return shape inline, plus mutation semantics, the save-success condition, and the effect-enabling precondition. That is everything an agent needs to call this 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 ssb_path, send_index (including resizing behavior), and the distance_curve JSON format. The description reinforces the growth/resize behavior but adds little syntax or format detail 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?

States a specific verb (merge/set) and a precisely named target: BusSends[send_index].CustomSendLevelCurve of a USoundSourceBus asset. It is clearly distinguishable from similarly named siblings like set_sound_source_bus_send_info and set_sound_source_bus_audio_bus.

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?

Provides a concrete usage precondition — the curve only takes effect when the send uses the CustomCurve control method — and routes the agent to set_sound_source_bus_send_info. It does not give an explicit when-not or list of alternatives, so it falls just short of a 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