Skip to main content
Glama

Voicedex

search_models

Read-onlyIdempotent

Search active speech models. Filters combine (AND). Paged: pass next_offset to get more.

language: BCP-47 code, e.g. "hi" or "en-GB". Only models that explicitly list it are returned, unless
include_unlisted_languages=true also adds models that claim "many languages" without listing them. capability: one feature term, e.g. "speaker_diarization",
"voice_cloning", "word_timestamps", "ssml". max_price_usd: upper bound on the normalized price (TTS per 1M
characters, STT/STS per hour); models without a comparable USD price are excluded when it is set.
sort: default "price" (cheapest first, announced shutdowns after the rest, unpriced last), or "eol_date"
(soonest end first) whenever shutting_down or eol_before is set. Shutdowns: shutting_down=true returns only
models with an announced end date; eol_before="YYYY-MM-DD" only those ending before it (e.g. "which models
shut down in the next 90 days?"). collapse_snapshots (default true) shows one row per model family (the
moving alias, e.g. gpt-realtime) and lists its dated snapshots (gpt-realtime-2025-08-28) in "snapshots";
pass false to get every snapshot as its own row.

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_models"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo
typeNo
limitNo
queryNo
offsetNo
regionNo
languageNo
providerNo
capabilityNo
eol_beforeNo
open_weightsNo
max_price_usdNo
shutting_downNo
collapse_snapshotsNo
include_unlisted_languagesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/closed-world, and the description adds substantial non-obvious behavior: filters AND-combine, paging, sort tiebreakers (announced shutdowns sorted after priced models, unpriced last), and that models without a comparable USD price are excluded when max_price_usd is set. One flaw: it says "pass next_offset" while the schema contains only "offset", leaving the paging handshake ambiguous. The collapse_snapshots explanation of returning one family row with a "snapshots" list is exactly the kind of detail annotations cannot carry.

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?

Front-loads purpose, AND-combination and paging in the first two sentences, then gives one compact passage per non-obvious parameter, so every sentence does work. The language sentence is dense and the next_offset/offset naming slip costs a little clarity.

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 shapes needn't be restated, and the tricky filter parameters are covered. Still, for a 15-parameter tool with zero schema descriptions, the filtering semantics of query, type, region, provider and open_weights are left entirely unstated, which is a real gap for an agent composing a search.

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?

Schema description coverage is 0%, so the description must carry the whole burden, and it does for the ambiguous parameters: language BCP-47 format with the include_unlisted_languages interaction, capability as a single feature term with examples, max_price_usd normalization basis (TTS per 1M chars, STT/STS per hour), eol_before format, and sort defaults. It leaves type, region, provider, open_weights, limit, offset and query undocumented, though most are self-explaining enum/boolean fields.

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 verb and resource ("Search active speech models") plus the scope word "active" and the AND-combination behavior. It does not differentiate from siblings such as get_model or compare_models, so an agent must infer that this is the browse/filter path rather than the detail path.

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?

Gives real usage rules for parameters (sort="eol_date" whenever shutting_down or eol_before is set; use eol_before for "which models shut down in the next 90 days?"; collapse_snapshots=false for every snapshot row). However, it never says when to use this tool instead of siblings like get_model or find_alternatives, so tool-selection guidance is only implied.

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.