Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

metasound_add_node_by_classname

Destructive

Instantiates a real DSP node in a MetaSound Source graph by registered class name, returning its GUID and pins so agents can wire a signal patch headless and save the asset.

Instructions

Add a real process node to a MetaSound Source graph by its registered class name (e.g. UE/Sine/Audio). Unlike add_metasound_graph_input (which adds a graph input node), this instantiates a DSP node so you can author a real signal patch headless. Returns the node's GUID (node_id) and its enumerated input/output pins (name + data_type) for follow-up set/connect calls. The asset is saved. NOT idempotent: each call adds a new node instance (delete + recreate the source for a clean run).

Returns: { asset_path: string, node_id: string, class_namespace: string, class_name: string, class_variant: string, inputs: [{name,data_type}], outputs: [{name,data_type}], added: bool, saved: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
class_nameYesRegistered node class name, e.g. "Sine".
class_variantNoOptional class variant, e.g. "Audio" (omit for the default/no-variant class).
major_versionNoOptional major version (default 1).
metasound_pathYesAsset path of the MetaSound Source.
class_namespaceYesRegistered node class namespace, e.g. "UE".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructive/not-idempotent/write semantics, and the description reinforces the non-idempotency plus adds context annotations cannot carry: the asset is auto-saved and each call creates a new node instance along with a remedy. It does not disclose permission requirements, which would push it higher.

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

Conciseness5/5

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

Front-loaded with purpose, then the sibling contrast, return payload, and the non-idempotency caveat last. Four tight clauses with no filler; every sentence contributes.

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?

No output schema exists, and the description fully documents the return payload (node_id, pin lists, saved flag) plus the follow-up workflow. Nothing an agent needs to invoke and chain the call is missing.

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 every parameter. The description's compound class example (UE/Sine/Audio) loosely maps to the namespace/class_name/class_variant triple but adds little beyond what the schema fields state, 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 ('Add') and resource ('real process node to a MetaSound Source graph') and immediately disambiguates from the sibling add_metasound_graph_input by noting this instantiates a DSP node rather than a graph input. The class name example (UE/Sine/Audio) makes the resource concrete.

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 names the alternative tool (add_metasound_graph_input) and the condition that distinguishes it, and describes the intended workflow — authoring a real signal patch headless followed by set/connect calls. It even gives the reset procedure (delete + recreate source) for a clean run.

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