Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_metasound_graph_input

Add a typed input to an existing MetaSound Source, optionally with a baked default, then save the asset in an undo transaction; use it to expose new graph parameters.

Instructions

Add a graph input of data_type (default Float) to an existing MetaSound Source through the MetaSound builder, inside an undo transaction, then save the asset. Optionally bakes a typed default into the new input; give at most one of default_value, int_value, bool_value or string_value (bool_value wins, then int_value, string_value, default_value). An unregistered data_type or a source that does not load is an error. A name already used by an input is left untouched: with the same data_type the call succeeds with added=false and already_exists=true, saves nothing and does not apply a supplied default (note says so; use metasound_set_input_default); with another data_type it is an error. success is false, with save_error, when the save fails (during PIE, for one). Inverse: remove_metasound_graph_input.

Returns: { asset_path: string, input_name: string, data_type: string, added: bool, already_exists?: bool, has_default: bool, note?: string, saved: bool, save_error: string? }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
data_typeNoFrontend data type: "Float", "Int32", "Bool", "String", "Audio", "Trigger" (optional, default "Float")
int_valueNoInt32 default baked into the literal (optional, mutually exclusive with other defaults)
bool_valueNoBool default baked into the literal (optional, mutually exclusive with other defaults)
input_nameYesName of the graph input node to add.
string_valueNoString default baked into the literal (optional, mutually exclusive with other defaults)
default_valueNoFloat default baked into the literal (optional)
metasound_pathYesAsset path of the MetaSound Source, as a package path like "/Game/MetaSounds/MS_Example" or an object path like "/Game/MetaSounds/MS_Example.MS_Example"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.2
    • changedInput schema / properties / metasound_path / description
      Previous value: -"Asset path of the MetaSound Source (e.g."New value: +"Asset path of the MetaSound Source, as a package path like \"/Game/MetaSounds/MS_Example\" or an object path like \"/Game/MetaSounds/MS_Example.MS_Example\""
  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 the write/non-destructive profile, but the description adds substantial context beyond them: the operation runs in an undo transaction, it saves the asset, saves can fail with save_error (e.g. during PIE), unregistered data_types fail, and the exact collision semantics. The default-precedence rule (bool_value > int_value > string_value > default_value) is behavior no annotation could convey.

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 core action is front-loaded and every sentence carries behavioral information, but the single dense paragraph with heavy parentheticals is a bit long and could be broken up for scanability. Nothing is wasted, though.

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 7-parameter mutating tool with no output schema, the description fully covers the return shape (asset_path, input_name, data_type, added, already_exists, has_default, note, saved, save_error), error states, and the inverse operation. An agent has everything needed to call it 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, but the description adds meaning beyond the schema by specifying the mutex precedence order among the default parameters and the semantics of an unregistered data_type — details the schema does not state. It does not explain the metasound_path format, but the schema already does.

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 opens with a precise verb+resource+scope: adding a graph input of a given data_type to an existing MetaSound Source via the builder, inside an undo transaction, then saving. It is immediately distinguishable from siblings like add_metasound_graph_output and remove_metasound_graph_input, and it names its own inverse.

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?

It gives explicit conditions and alternatives: at most one default argument may be supplied, an already-existing name with a matching data_type is a no-op (added=false, already_exists=true) and the agent should instead use metasound_set_input_default, while a name collision with a different data_type is an error. This tells the agent both when to call it and when to route elsewhere.

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