Skip to main content
Glama

aw.audio.reverse

Reverse every channel with the actual AudioWrench core; verified new PCM WAV.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session": "<session>",
      "operationId": "<operationId>",
      "source": "<source>"
    },
    "name": "aw.audio.reverse"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesAn immutable input or result handle belonging to this session; never a URL/path/base64.
float32No
sessionYesPrivate short-lived session capability returned by aw.session.open. Never publish or log it.
operationIdYesStable operation UUID for safe retry/reconciliation; reuse only with identical sources/settings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so safety is partly covered. The description adds genuinely useful context beyond them: the operation applies to *every* channel and emits a *new* WAV (consistent with non-destructive), and 'verified' hints at an integrity check. It omits what the return value is (handle vs. operation record), whether the source handle is consumed, and what float32 changes.

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?

A single short sentence fragment with the transformation front-loaded and no filler. The phrase 'with the actual AudioWrench core' is vague marketing tone that spends words without informing the agent, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must explain what comes back; 'verified new PCM WAV' gestures at the artifact but never says how to retrieve or reference it (a new source handle, presumably). For a session-bound audio mutation tool with four parameters, that is a meaningful gap but not a fatal one.

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 75% and the schema already explains source, session and operationId in detail, so the baseline is 3. The description contributes only the implicit hint that output defaults to PCM WAV, adding essentially nothing about the four parameters beyond the structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource is specific: 'Reverse every channel' names the exact transformation and its channel scope, and 'new PCM WAV' names the product. It does not, however, distinguish itself from the only similar sibling (aw.audio.trim) or state the input handle model, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use / when-not-to-use guidance, no mention of alternatives such as aw.audio.trim, and no stated prerequisite that a session must be open and a source handle obtained first. Usage is only inferable from the tool name and the parameter names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources