Skip to main content
Glama

text_to_speech

Convert written text into spoken audio files. Specify the text, output path, and optionally choose voice and model.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesText to convert to speech
output_pathYesAbsolute path to write the output audio file (e.g. /tmp/output.mp3)
voiceNoVoice ID to use. Defaults to af_heart
modelNoTTS model ID to use. Defaults to speaches-ai/Kokoro-82M-v1.0-ONNX

Implementation Reference

  • src/index.js:66-112 (registration)
    The `text_to_speech` tool is registered on the MCP server via `server.tool(...)`. It accepts text, output_path, optional voice, and optional model parameters. The handler calls the OpenAI-compatible TTS API, writes the audio buffer to disk, and returns a confirmation message.
    server.tool(
      "text_to_speech",
      {
        text: z.string().describe("Text to convert to speech"),
        output_path: z
          .string()
          .describe("Absolute path to write the output audio file (e.g. /tmp/output.mp3)"),
        voice: z
          .string()
          .optional()
          .describe(`Voice ID to use. Defaults to ${TTS_VOICE}`),
        model: z
          .string()
          .optional()
          .describe(`TTS model ID to use. Defaults to ${TTS_MODEL}`),
      },
      async ({ text, output_path, voice, model }) => {
        const dir = path.dirname(output_path);
        if (!fs.existsSync(dir)) {
          return {
            content: [{ type: "text", text: `Error: output directory does not exist: ${dir}` }],
            isError: true,
          };
        }
    
        let buffer;
        try {
          const response = await client.audio.speech.create({
            model: model || TTS_MODEL,
            voice: voice || TTS_VOICE,
            input: text,
          });
          buffer = Buffer.from(await response.arrayBuffer());
        } catch (err) {
          return {
            content: [{ type: "text", text: `Error: TTS failed: ${err.message}` }],
            isError: true,
          };
        }
    
        fs.writeFileSync(output_path, buffer);
    
        return {
          content: [{ type: "text", text: `Audio saved to ${output_path}` }],
        };
      }
    );
  • Input schema for the `text_to_speech` tool, defined using Zod: `text` (required string), `output_path` (required string), `voice` (optional string, defaults to TTS_VOICE env var), and `model` (optional string, defaults to TTS_MODEL env var).
    {
      text: z.string().describe("Text to convert to speech"),
      output_path: z
        .string()
        .describe("Absolute path to write the output audio file (e.g. /tmp/output.mp3)"),
      voice: z
        .string()
        .optional()
        .describe(`Voice ID to use. Defaults to ${TTS_VOICE}`),
      model: z
        .string()
        .optional()
        .describe(`TTS model ID to use. Defaults to ${TTS_MODEL}`),
    },
  • The handler function for `text_to_speech`. It validates the output directory exists, calls `client.audio.speech.create()` (OpenAI-compatible TTS API), buffers the response, writes it to the output file, and returns a success or error message.
    async ({ text, output_path, voice, model }) => {
      const dir = path.dirname(output_path);
      if (!fs.existsSync(dir)) {
        return {
          content: [{ type: "text", text: `Error: output directory does not exist: ${dir}` }],
          isError: true,
        };
      }
    
      let buffer;
      try {
        const response = await client.audio.speech.create({
          model: model || TTS_MODEL,
          voice: voice || TTS_VOICE,
          input: text,
        });
        buffer = Buffer.from(await response.arrayBuffer());
      } catch (err) {
        return {
          content: [{ type: "text", text: `Error: TTS failed: ${err.message}` }],
          isError: true,
        };
      }
    
      fs.writeFileSync(output_path, buffer);
    
      return {
        content: [{ type: "text", text: `Audio saved to ${output_path}` }],
      };
    }
Behavior1/5

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

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

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/xavier-hernandez/mcp-speaches'

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