Skip to main content
Glama

AQuA: compare with a reference

aqua_compare
Read-only

Intrusive voice quality analysis (Sevana AQuA, wideband): compares a degraded/test WAV with its reference WAV and returns MOS, percent similarity and a fault analysis explaining the loss of quality. Upload both files first.

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": {
      "reference_upload_id": "<reference_upload_id>",
      "test_upload_id": "<test_upload_id>"
    },
    "name": "aqua_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
channel_testNotest channel, from 0 (default: AQuA's choice)
test_upload_idYesupload_id of the degraded/test WAV
channel_referenceNoreference channel, from 0 (default: AQuA's choice)
reference_upload_idYesupload_id of the original/reference WAV

Output Schema

NameRequiredDescriptionDefault
mosYesAQuA MOS (1-5)
faultsYesAQuA's fault analysis: why quality is lost (delay, spectrum, level, noise), with per-file values
percentYessimilarity of the test file to the reference, 0-100
test_upload_idYes
reference_upload_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is read-only and closed-world, so the safety profile is covered. The description adds meaningful behavior beyond annotations: it identifies the analysis as intrusive and wideband and names the returned MOS, percent similarity, and fault analysis explaining quality loss.

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?

Two sentences with no wasted wording. The core purpose is front-loaded, and the upload prerequisite follows directly.

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

Completeness4/5

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

Given the annotations and the existence of an output schema, the description covers the essential purpose, required inputs, and expected output themes. It is complete enough to invoke the tool correctly, though it could mention runtime or job behavior.

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 all four parameters are already documented in the schema. The description maps the reference and test upload IDs to their real-world meaning, but it does not add guidance for the channel parameters beyond what the schema provides.

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 description gives a specific verb and resource: it 'compares a degraded/test WAV with its reference WAV' using Sevana AQuA wideband intrusive analysis. It clearly states what the tool does, but it does not explicitly name or differentiate itself from sibling tools such as pvqa_analyze.

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?

The prerequisite 'Upload both files first' gives clear operational context, and 'intrusive' implies a reference WAV is required. It stops short of stating when to prefer this over alternatives or when not to use it.

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