Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_meta_sound_node_info

Read-onlyIdempotent

Read one MetaSound Source graph node by GUID to get its name, class, input/output/environment vertices, literal defaults, and config class. Get node ids from list_meta_sound_nodes.

Instructions

Read one node of the default graph of a MetaSound Source by GUID: its name, class name, input/output/environment vertices (name, type_name, vertex_id), input literal defaults and Configuration struct class. Read-only; get node ids from list_meta_sound_nodes.

Returns: { metasound_path, node_id, name, class_name, inputs: [{name, type_name}], outputs: [...], environment: [...], input_defaults: [{vertex_id, value, type}], configuration_class }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idYesNode GUID, as list_meta_sound_nodes returns it in id; a value that is not a GUID is refused.
metasound_pathYesMetaSound Source asset path, e.g. "/Game/Audio/MS_Rain"; MetaSound Patches are not accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • changedInput schema / properties / metasound_path / description
      Previous value: -"Asset path."New value: +"MetaSound Source asset path, e.g. \"/Game/Audio/MS_Rain\"; MetaSound Patches are not accepted."
    • changedInput schema / properties / node_id / description
      Previous value: -"Node GUID string."New value: +"Node GUID, as list_meta_sound_nodes returns it in id; a value that is not a GUID is refused."
  2. First observedv1.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds value by scoping behavior to the 'default graph' only and by disclosing the full returned structure (vertices, literals, configuration class), which is the main behavioral disclosure an agent needs.

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?

Purpose is front-loaded in the first sentence, followed by a compact Returns shape. Every clause earns its place; no filler or redundant restatement of the name.

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 steps in and specifies the return object field-by-field. Combined with the prerequisite guidance and 100% schema coverage on params, an agent has everything needed to call it 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 coverage is 100%, so both params (node_id, metasound_path) are already fully documented in the schema, including the GUID format and path example. The description's 'by GUID' and id-source note largely restate the schema, so baseline 3 is appropriate.

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 ('Read one node of the default graph of a MetaSound Source by GUID') and enumerates exactly what it returns (name, class name, input/output/environment vertices, defaults, configuration class). An agent can distinguish it from sibling list_meta_sound_nodes, which it names as the id source.

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 clear usage context by naming the prerequisite sibling ('get node ids from list_meta_sound_nodes') and the read-only nature. It does not explicitly contrast with sibling node-inspection tools like get_meta_sound_node_property or get_meta_sound_node_input_default, so no exclusions are stated, 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