Skip to main content
Glama

Voicedex

search_voices

Read-onlyIdempotent

Search stock voices (15,000+, so results are compact and paged: pass next_offset for more). model: a model id of that provider (voices compatible with it). has_sample=true returns only voices with an audio preview URL.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
modelNo
queryNo
genderNo
offsetNo
languageNo
providerNo
has_sampleNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already cover read-only, idempotent, non-open-world behavior, so the description only needs to add context. It does explain the 15,000+ corpus, that results are compact and paged, and that has_sample restricts to voices with an audio preview URL — real value. It stops short of explaining what happens with unknown providers/models or how 'query' matching works.

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?

Three short, front-loaded segments with no filler, and the scale/paging constraint comes first. The telegraphic 'model:' and 'has_sample=' fragments are slightly choppy but still readable.

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-value explanation is unnecessary, and the description does give enough to issue a basic unfiltered or has_sample-filtered search. However, five of eight parameters are undocumented in both schema and description, and the pagination field is misnamed, which leaves real holes for a search tool with this many facets.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries full burden across 8 parameters, yet it explains only 'model' and 'has_sample'. It also refers to 'next_offset' where the schema defines 'offset', which is actively misleading. query, gender, language, provider, and limit are left entirely undefined.

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 first clause names a specific verb and resource ('Search stock voices') and adds scale context (15,000+ entries). It is clear what the tool returns, though it does not contrast itself with any sibling such as search_models; the resource difference is obvious enough that this is a minor gap.

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

Usage Guidelines2/5

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

There is a hint about paging ('results are compact and paged: pass next_offset for more'), but the parameter is actually named 'offset' in the schema, so the guidance points at a field an agent cannot pass. No guidance on when to prefer this over alternatives, or on how filters combine.

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.