Skip to main content
Glama

listAudioVoices

Retrieve the complete list of available voices for text-to-speech generation. Use this to select the appropriate voice for your audio output.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler for listAudioVoices. Returns a list of available audio voices (alloy, echo, fable, onyx, nova, shimmer, coral, verse, ballad, ash, sage, amuch, dan).
    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 };
    }
  • Schema definition for listAudioVoices tool. Name: 'listAudioVoices', description: 'List all available audio voices for text-to-speech generation', no input parameters.
    export const listAudioVoicesSchema = {
      name: 'listAudioVoices',
      description: 'List all available audio voices for text-to-speech generation',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    };
  • MCP server handler routing for the 'listAudioVoices' tool call. Invokes listAudioVoices() and returns the result as JSON text content.
    } 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:21-26 (registration)
    Central schema export: re-exports listAudioVoicesSchema and includes it in getAllToolSchemas() for MCP tool registration.
      listAudioVoicesSchema,
    
      // Text schemas
      respondTextSchema,
      listTextModelsSchema
    };
  • Re-exports listAudioVoices from audioService.js so it can be imported by the MCP server.
      // Audio services
      respondAudio,
      listAudioVoices,
    
      // Text services
      respondText,
      listTextModels,
    };
Behavior3/5

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

With no annotations, the description carries full burden for behavioral disclosure. It implies a read-only operation but does not mention side effects, permissions, rate limits, or return format. For a simple list tool, this is adequate but incomplete.

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 sentence that conveys the core purpose without any fluff. It is appropriately concise and front-loaded.

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?

Given the tool's simplicity (no parameters, no output schema), the description is mostly complete. However, it could briefly mention the expected return type or that the list includes all voices, which would improve completeness.

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 zero parameters and schema coverage is 100%. The description adds no parameter details, but the baseline for 0 parameters is 4, and no additional explanation is needed.

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), resource (audio voices), and context (for text-to-speech generation). It effectively distinguishes from sibling tools, which are mostly image-related, making the purpose unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any prerequisites, exclusion cases, or comparisons with other list tools on the same server.

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