Skip to main content
Glama

listAudioVoices

Discover available text-to-speech voices to select the right audio option for your content generation needs.

Instructions

List all available audio voices for text-to-speech generation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function implementing listAudioVoices tool logic, returning a hardcoded list of available TTS voices.
    /**
     * List available audio voices
     *
     * @returns {Promise<Object>} - Object containing the list of available voice options
     */
    export async function listAudioVoices() {
      // Return the complete list of available voices
      const voices = [
        "alloy",
        "echo",
        "fable",
        "onyx",
        "nova",
        "shimmer",
        "coral",
        "verse",
        "ballad",
        "ash",
        "sage",
        "amuch",
        "dan"
      ];
    
      return { voices };
    }
  • JSON schema defining the listAudioVoices tool, including name, description, and empty input schema (no parameters required).
    /**
     * Schema for the listAudioVoices tool
     */
    export const listAudioVoicesSchema = {
      name: 'listAudioVoices',
      description: 'List all available audio voices for text-to-speech generation',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    };
  • MCP server dispatch handler that executes listAudioVoices tool upon matching tool name and formats the response.
    } else if (name === 'listAudioVoices') {
      try {
        const result = await listAudioVoices();
        return {
          content: [
            { type: 'text', text: JSON.stringify(result, null, 2) }
          ]
        };
      } catch (error) {
        return {
          content: [
            { type: 'text', text: `Error listing audio voices: ${error.message}` }
          ],
          isError: true
        };
      }
  • src/schemas.js:28-44 (registration)
    Central function registering all tool schemas (including listAudioVoicesSchema) for the MCP ListTools endpoint.
    /**
     * Get all tool schemas as an array
     * @returns {Array} Array of all tool schemas
     */
    export function getAllToolSchemas() {
      return [
        generateImageUrlSchema,
        generateImageSchema,
        editImageSchema,
        generateImageFromReferenceSchema,
        listImageModelsSchema,
        respondAudioSchema,
        listAudioVoicesSchema,
        respondTextSchema,
        listTextModelsSchema
      ];
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('List all available audio voices') but doesn't describe traits like whether the list is paginated, sorted, includes metadata, or has rate limits. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to understand at a glance.

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?

Given the tool's low complexity (0 parameters, no output schema), the description is minimally adequate but lacks details on behavioral aspects like return format or usage context. Without annotations or output schema, it should provide more context about what the list includes and how to use it, but it meets the basic requirement for a simple listing tool.

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?

The tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The baseline for this scenario is 4, as the description appropriately doesn't add unnecessary parameter information, though it could briefly note the lack of parameters for clarity.

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 description clearly states the verb ('List') and resource ('all available audio voices for text-to-speech generation'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'listImageModels' or 'listTextModels' beyond the domain specificity, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives, such as whether it should be called before selecting a voice for 'respondAudio' or how it relates to other list tools. There's only an implied context from the domain, but no explicit usage instructions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pinkpixel-dev/MCPollinations'

If you have feedback or need assistance with the MCP directory API, please join our Discord server