Skip to main content
Glama

Sevana Voice Quality

PVQA: raw detector values

pvqa_detector
Read-only

Raw values of one PVQA detector over time for an uploaded WAV file. Detectors: SNR, DeadAir-00, DeadAir-01, Click, VADClip, AmpClip, DynClip, Echo, Noise, Crushed, DTMF.

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": {
      "upload_id": "<upload_id>",
      "detector": "<detector>"
    },
    "name": "pvqa_detector"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNochannel to analyze, from 0 (default 0)
detectorYesdetector name: SNR, DeadAir-00, DeadAir-01, Click, VADClip, AmpClip, DynClip, Echo, Noise, Crushed or DTMF
upload_idYesupload_id of a WAV file

Output Schema

NameRequiredDescriptionDefault
rowsYes
namesYesvalue names; the first is the detector's main value
detectorYes
upload_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish that this is read-only, closed-world, and not idempotent. The description adds useful behavioral context by specifying that results are raw values over time and by listing valid detectors, but it does not add operational details such as rate limits or authentication requirements; the output schema covers return values.

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?

The description is two sentences and front-loads the core purpose in the first sentence. The second sentence's detector list is compact but largely duplicates the detector parameter description in the schema.

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 full schema coverage, read-only annotations, and an available output schema, the description provides enough information for an agent to invoke the tool correctly. Its main gap is the absence of routing guidance relative to sibling PVQA analysis tools.

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 input schema already documents upload_id, detector, and channel. The description repeats the detector list and the 'one detector' constraint, but adds no meaning 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 specifically identifies the operation as retrieving 'Raw values of one PVQA detector over time for an uploaded WAV file.' The phrase 'one PVQA detector' distinguishes it from broader aggregate analysis, though it does not explicitly name sibling tools such as pvqa_analyze or pvqa_timeline.

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

Usage Guidelines3/5

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

Usage is implied: use this when you need raw per-detector values for an uploaded WAV file rather than a summarized report. However, there is no explicit guidance about when to choose this over pvqa_analyze or pvqa_timeline, and no when-not-to-use conditions are stated.

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