Skip to main content
Glama

list_voices

Retrieve available text-to-speech voices for use with macOS speech commands, enabling precise voice selection in applications.

Instructions

List available text-to-speech voices

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the list_voices tool: executes 'say -v "?"' to list macOS TTS voices and returns the stdout as text content, with error handling.
    case 'list_voices': {
      try {
        const { stdout } = await execAsync('say -v "?"');
        return {
          content: [
            {
              type: 'text',
              text: stdout,
            },
          ],
        };
      } catch (error: any) {
        throw new McpError(
          ErrorCode.InternalError,
          `Failed to list voices: ${error.message}`
        );
      }
    }
  • src/index.ts:75-82 (registration)
    Registration of the list_voices tool in the ListToolsRequestSchema response, including name, description, and input schema (no required params).
    {
      name: 'list_voices',
      description: 'List available text-to-speech voices',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema for list_voices tool: empty object schema (no parameters).
    inputSchema: {
      type: 'object',
      properties: {},
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but doesn't describe what the output looks like (e.g., list format, voice attributes), whether it's cached, or any rate limits. This leaves significant gaps for an agent to understand the tool's 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 with no wasted words. It's appropriately sized for a simple tool and front-loads the core purpose immediately.

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?

For a simple, parameterless tool with no output schema, the description is minimally adequate. However, it lacks details about the output format or behavioral traits, which would help an agent use it correctly. Without annotations, the description should do more to compensate.

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% (though empty). The description doesn't need to add parameter details, so it meets the baseline expectation for a parameterless tool without compensation 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') and resource ('available text-to-speech voices'), making the tool's purpose immediately understandable. It doesn't explicitly differentiate from its sibling 'speak', but the distinction is reasonably implied (listing vs. using voices).

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 its sibling 'speak' or any alternatives. The description only states what it does, not when it should be selected over other options.

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

Related Tools

  • @samihalawa/advanced-tts-mcp
  • @turlockmike/apple-notifier-mcp
  • @bmorphism/say-mcp-server
  • @hammeiam/koroko-speech-mcp
  • @johnmatthewtennant/mcp-voice-hooks
  • @Yuki10Kobayashi/voicevox-mcp

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/bmorphism/say-mcp-server'

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