Skip to main content
Glama
Omnidim

@omnidim-ai/mcp-server

by Omnidim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

listVoices

Read-only

Retrieve paginated text-to-speech voices and filter by provider, name, language, accent, or gender where supported to choose voices for voice agents.

Instructions

Retrieve voices with filtering and pagination support. ElevenLabs and Cartesia support advanced filtering by name, language, accent, and gender. Other providers support basic pagination only.

(Tags: Providers)

Input Schema

NameRequiredDescriptionDefault
pageNo1-indexed page number.
accentNoAccent label (e.g. `american`, `british`). ElevenLabs and Cartesia.
genderNoFilter voices by gender. ElevenLabs and Cartesia.
searchNoSubstring match against voice name or description. ElevenLabs and Cartesia.
languageNoISO language code (e.g. `en`, `hi`, `es`). ElevenLabs and Cartesia.
providerNoTTS provider to list voices from. Omit to list across all providers.
page_sizeNoVoices per page. Capped at 100.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.14.0
    • changedInput schema / properties / accent / description
      Previous value: -"Accent label (e.g. `american`, `british`). ElevenLabs only."New value: +"Accent label (e.g. `american`, `british`). ElevenLabs and Cartesia."
    • changedInput schema / properties / gender / description
      Previous value: -"Filter voices by gender. ElevenLabs only."New value: +"Filter voices by gender. ElevenLabs and Cartesia."
    • changedInput schema / properties / language / description
      Previous value: -"ISO language code (e.g. `en`, `hi`, `es`). ElevenLabs only."New value: +"ISO language code (e.g. `en`, `hi`, `es`). ElevenLabs and Cartesia."
    • changedInput schema / properties / provider / enum
      Previous value: -[
-  "eleven_labs",
-  "google",
-  "deepgram",
-  "cartesia",
-  "sarvam"
-]New value: +[
+  "eleven_labs",
+  "google",
+  "deepgram",
+  "cartesia",
+  "sarvam",
+  "rime",
+  "playht",
+  "hume",
+  "inworld",
+  "smallest"
+]
    • changedInput schema / properties / search / description
      Previous value: -"Substring match against voice name or description. ElevenLabs only."New value: +"Substring match against voice name or description. ElevenLabs and Cartesia."
  2. First observedv0.9.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is lower. The description adds a genuinely non-obvious behavioral trait: filtering support is provider-conditional, and non-ElevenLabs/Cartesia providers degrade to pagination-only. It omits whether unsupported filters are silently ignored or error out.

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 compact sentences front-load the capability and then the provider-conditional caveat; nothing is redundant. The trailing "(Tags: Providers)" is low-value noise but minor.

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 7-parameter, no-required-argument list tool with no output schema and annotations covering safety, the description supplies the one thing structured fields cannot: provider-dependent filtering behavior. The only real gap is the outcome when a filter is passed to an unsupported provider.

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 in the schema with types, enums, defaults, and provider notes. The description's mention of name/language/accent/gender filters merely restates that coverage and adds no syntax or semantics beyond it, so the baseline 3 applies.

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 ("Retrieve") and resource ("voices") and pairs it with the filtering/pagination scope, which distinguishes it from getVoice (single) and listClonedVoices (cloned subset). It stops short of naming those siblings explicitly, so the differentiation is inferable rather than stated.

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?

It gives useful context that advanced name/language/accent/gender filtering only applies to ElevenLabs and Cartesia while other providers support pagination only, effectively telling the agent when a filter will have an effect. However, it never says when to pick this over getVoice or listClonedVoices, so alternative selection is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools