Establishes a TCP connection to the UE5 audio plugin, enabling AI-driven game audio creation for Unreal Engine through Wwise and MetaSounds integration.
Connect to the UE5 audio plugin via TCP.
Args: host: Plugin host address (default 127.0.0.1) port: Plugin TCP port (default 9877)
| Name | Required | Description | Default |
|---|---|---|---|
| host | No | 127.0.0.1 | |
| port | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.0.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the transport (TCP), which is useful, but says nothing about failure behavior, timeouts, whether an existing connection is replaced, or whether the connection persists across calls—important traits for a stateful connection tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The core action is front-loaded in the first sentence and the args block is compact with no filler. The docstring-style Args formatting is slightly redundant since the parameter names already appear in the schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained, and both parameters are documented. Still, for a connection tool with no annotations, the description omits the connection lifecycle and error semantics an agent would need to invoke it reliably.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate, and it does define both parameters semantically ('Plugin host address', 'Plugin TCP port'). However, the stated defaults duplicate the schema defaults and no format or validation guidance (e.g., hostname vs IP, port range) is added.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Connect to the UE5 audio plugin via TCP'), so the operation is unambiguous. It does not differentiate from the sibling wwise_connect, which offers an analogous connection operation, so an agent cannot tell from the description alone which endpoint to target.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to call this versus alternatives such as wwise_connect, nor any prerequisites (does a session need to be started first? must the plugin be running?). Usage is only implied by the verb 'connect'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.