Skip to main content
Glama
ollama-tts-mcp

ollama-tts-mcp

speak

Converts text into offline audio played through local speakers, queues playback, and supports voice/model selection for on-device text-to-speech.

Instructions

Say text out loud through this computer's speakers, fully offline.

Use it when the user asks you to speak, read something aloud, or announce a result. Markdown, code blocks and URLs are tidied up before speaking. Playback runs in the background and queues behind anything already playing; call stop_speaking to cut it off.

Args: text: What to say. Any length; long text is split at sentence boundaries. voice: Voice name, case-insensitive (e.g. "Zoey", "Hugh", "Freya"). Defaults to the configured voice. See list_voices. model: Ollama speech model tag, e.g. "phonon" or "phonon:multilingual". Defaults to the configured model. wait: If true, return only after the audio has finished playing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "speak"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
waitNo
modelNo
voiceNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and largely succeeds: it discloses offline operation, background/queued playback, markdown and URL cleanup, and sentence-boundary splitting of long text. It omits failure behavior, e.g. what happens if the model or requested voice is unavailable.

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?

The summary is front-loaded in two tight sentences, then the Args block adds per-parameter detail without filler. The docstring formatting is slightly verbose for a tool description, but every line carries usable information.

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

Completeness5/5

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

For a four-parameter playback tool with an output schema already covering return values, the description supplies everything an agent needs: when to call it, how playback behaves, the interruption path, and full parameter semantics including defaults and cross-references.

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

Parameters5/5

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

Schema coverage is 0%, so the description must supply all parameter meaning — and it does for all four: `text` accepts any length, `voice` is case-insensitive with examples and a configured default, `model` gives concrete Ollama tags, and `wait` is defined as blocking until playback finishes.

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 first sentence gives a concrete verb and resource: "Say text out loud through this computer's speakers," plus the offline constraint. It reads clearly as local playback rather than audio-file generation, though it never explicitly contrasts with the `text_to_speech` sibling, so the boundary between the two is left implicit.

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

Usage Guidelines4/5

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

It states explicit triggers — user asks to speak, read aloud, or announce a result — and points to `stop_speaking` for interruption and `list_voices` for voice discovery. Missing is when NOT to use it, in particular how it differs from the `text_to_speech` alternative.

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