voice-quality-api
Server Details
Measure voice/VoIP path quality -> estimated MOS + live network metrics
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.1/5 across 1 of 1 tools scored.
With only one tool, there is no possibility of ambiguity or confusion between tools.
A single tool ensures perfect naming consistency, as there is only one name to evaluate.
One tool is slightly below the typical range but is well-scoped for measuring voice quality, making it reasonable for a focused API.
The tool covers the core functionality of measuring voice quality with key metrics, though additional features like history or configuration are absent.
Available Tools
1 toolmeasure_voice_qualityMeasure voice qualityAInspect
Measure the quality of a voice/VoIP path to a destination and return the estimated MOS (ITU-T G.107 E-model) plus live network metrics (RTT, jitter, packet loss). Useful before routing or starting a voice-agent call. The MOS is an objective estimate, not a perceptual measurement.
| Name | Required | Description | Default |
|---|---|---|---|
| from | No | Optional probe location selectors, e.g. ['eu-west','us-east'] | |
| codec | No | Narrowband codec to model | G711 |
| target | Yes | IP, host, or media endpoint to measure toward |
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses that the MOS is an objective estimate and returns network metrics. It does not mention potential side effects (none expected) or prerequisites, which is acceptable for a read-like measurement 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?
Three sentences: first describes the action and return, second gives usage guidance, third provides a caveat. Every sentence adds value, and the key information is front-loaded.
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?
Given no output schema, the description adequately explains the return values (MOS, RTT, jitter, packet loss). Parameters are fully documented in the schema, and the tool's purpose and context are fully covered.
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 coverage is 100%, so baseline is 3. The description adds no parameter details beyond the schema; it only mentions 'target' implicitly in the main action. No extra value is provided over the structured input schema.
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?
The description clearly states the tool measures voice quality of a VoIP path and returns specific metrics (MOS, RTT, jitter, packet loss). It uses a specific verb 'Measure' and resource, leaving no ambiguity about its function.
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?
Provides explicit usage context: 'Useful before routing or starting a voice-agent call.' However, it does not mention when not to use it or alternative tools, though no siblings exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!