Skip to main content
Glama

search_voices

Read-onlyIdempotent

Unified voice search across one or more TTS providers. Every result is normalized to { voiceId, name, provider, previewUrl, filters: { accent, gender, useCase, language } }. Use this when the user asks for a voice by gender / language / accent without caring which provider. Read-only — does NOT consume credits.

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
limitNoPage size, 1–500. Default 100.
accentNoSubstring match, e.g. "american", "british".
genderNomale / female / neutral. Aliases m / f / masculine / feminine accepted.
offsetNoPagination offset. Default 0.
modelIdNoFilter to a specific TTS model id when relevant.
languageNoInclusive match: "en" matches "en-US", "en-GB", "English". Use BCP-47 codes or English names.
providersNoComma-separated provider slugs to limit the search (e.g. "elevenlabs,cartesia"). Omit for all providers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds two valuable non-schema facts: that it does not consume credits and what the normalized result record looks like. It stops short of describing pagination behavior or result ordering, which keeps it from a 5.

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?

Two sentences, zero waste, with the scope and normalized result shape front-loaded ahead of the cost note. Every sentence earns its place.

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?

With no output schema, the description supplies the return record shape, which is genuinely necessary. Scope, cost, and usage are all covered; only pagination/results ordering is left implied by the schema.

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 coverage is 100%, so every parameter is already documented with matching rules and aliases. The description adds only the high-level notion of filtering by gender/language/accent, no syntax or format detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Unified voice search across one or more TTS providers') and immediately informs the agent that results are provider-agnostic, which separates it from provider-specific siblings like list_provider_voices and list_voice_models.

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

Usage Guidelines4/5

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

Explicitly gives the triggering condition: use when the user asks for a voice by gender/language/accent without caring which provider. It doesn't state when to prefer the sibling tools instead, but the condition is clear enough to route correctly.

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