Skip to main content
Glama
ollama-tts-mcp

ollama-tts-mcp

list_voices

Lists voices available in an Ollama speech model and installed speech models so you can pick the right voice for text-to-speech.

Instructions

List the voices available in an Ollama speech model, and the speech models installed.

Args: model: Speech model tag to inspect. Defaults to the configured model.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_voices"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It implies a read-only enumeration and states the model defaults to the configured one, but says nothing about whether it contacts a local Ollama server, what happens with an unknown model tag, or whether the call can fail or be slow.

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 prose sentence is front-loaded and the parameter note is short and specific. The raw 'Args:' block is slightly awkward in a description field but adds real information rather than padding.

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?

For a one-parameter, non-destructive listing tool with an output schema covering return values, the description covers the action, both listed resources, and the parameter default. Only error/failure behavior is absent, which is a minor gap.

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?

Schema description coverage is 0%, so the description must carry the parameter. It does: the single 'model' argument is explained as a speech model tag to inspect, and the default behavior (falls back to the configured model) is stated, which the schema only expresses as a null default.

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 gives a specific verb ('List') and two concrete resources: the voices available in an Ollama speech model and the installed speech models. This is enough to distinguish it from the speaking siblings (speak, text_to_speech), though it never names them explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the discovery/inspection step before choosing a voice for the speech tools. There is no explicit statement of when to use this versus the siblings, and no prerequisites or exclusions are given.

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