Skip to main content
Glama

Sevana Voice Quality

Server, limits and quota

server_info
Read-only

Analyzer versions, your tier (free or API key), your limits and how many analyses you have left.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "server_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
roleYes
tierYes"free" (no API key) or "api_key"
limitsYes
serverYes
key_nameNo
analyzersYesanalyzer name -> version
upload_ttl_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered and the description is not required to restate them. The remaining sentences add only the subject matter of the response (versions, tier, limits, remaining count) rather than behavior such as whether the quota figure is per-period or how it is refreshed. Since an output schema exists, that gap is tolerable rather than serious.

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?

A single front-loaded sentence with no filler; every listed item (versions, tier, limits, remaining analyses) earns its place and maps to a distinct piece of returned information.

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?

For a zero-parameter, read-only info tool with an output schema and full annotation coverage, almost nothing must be explained in prose, and the description enumerates the four things an agent would care about. Only a note on when to consult it is missing, which is a usage concern rather than a completeness hole in the payload description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline of 4 applies. There is nothing for the description to clarify about inputs, and it does not waste words pretending otherwise.

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 names the resource precisely: analyzer versions, caller tier (free vs API key), limits, and remaining analyses. That is concrete enough for an agent to know this is a read-only account/server metadata probe, distinct from the pcap_*/pvqa_* analysis siblings. It stops short of a singular verb phrase, but the noun list is specific.

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 only implied: an agent can infer it should call this to check quota before kicking off analyses, but the description never says when to use it or names any alternative. With no parameters and no exclusions given, the agent must supply the when- and why- itself.

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