Skip to main content
Glama

Voicedex

list_providers

Read-onlyIdempotent

Providers in the catalog with model and voice counts, headquarters and access model. Retired providers (shut down or no longer sold) are included only when include_retired=true, with their retirement date.

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": "list_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
include_retiredNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, closed-world behavior, and the description adds real value: it discloses the returned fields and the important default that retired providers are excluded unless include_retired=true, along with the retirement date. It does not mention ordering, pagination, or the effect of the type filter.

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?

Two tight sentences, with the catalog contents front-loaded and the retirement caveat second. No filler, though the phrasing is dense enough that the type filter is silently dropped.

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?

An output schema exists, so return values need not be spelled out, yet the description is still incomplete for a two-parameter listing tool because the type filter is unexplained and there is no routing guidance among the many sibling search/get 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 0%, so the description must carry the burden. It explains include_retired well, including the default exclusion of retired providers, but says nothing about the 'type' parameter and its stt/tts/sts values, leaving one of two parameters undocumented.

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?

States a specific resource (providers in the catalog) and the fields returned: model and voice counts, headquarters, and access model. It is clearly distinct from sibling tools like get_model or search_voices, though it never names an alternative explicitly.

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?

The retirement sentence gives a concrete rule for when retired providers appear (include_retired=true), but there is no explicit guidance on when to use this tool instead of siblings such as compare_models or find_alternatives. Usage is only implied by the resource being listed.

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.