Skip to main content
Glama
ahamed-kashif

text-to-speech

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TTS_OUTPUT_DIRNoWhere MP3s are written when no output_path is given./output
TTS_MAX_RETRIESNoMax synthesis attempts before failing3
TTS_DEFAULT_LANGNoDefault language codeen
TTS_RETRY_BACKOFFNoBase backoff seconds (1s, 2s, 4s, …)1.0
TTS_DEFAULT_ACCENTNoDefault accent TLDcom

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
text_to_speechA

Convert text into spoken audio (MP3) using Google TTS (gTTS).

Args:
    text: The text to speak. Required, must be non-empty.
    language: Language code such as "en", "bn", "es". Defaults to "en".
    slow: Speak more slowly when True.
    accent: Google domain TLD controlling accent for some languages,
        e.g. "com" (US), "co.uk" (UK), "com.au" (AU), "co.in" (India).
    output_path: Where to write the MP3. If omitted, a timestamped file
        is created under the configured output directory.

Returns:
    A human-readable status string including the saved file path, or an
    "Error: ..." message describing what went wrong.
list_languagesA

List the language codes and names supported for text_to_speech.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one lists supported languages, and the other converts text to speech. There is no overlap or ambiguity.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern (list_languages, text_to_speech), making the naming predictable and intuitive.

Tool Count3/5

With only two tools, the server is quite thin but still covers the core functionality for a simple text-to-speech service. The count is borderline for the domain.

Completeness4/5

The domain is well-covered by listing languages and converting text to speech with various options. No major gaps are apparent, though additional settings tools could be added.

Maintenance

ActivityInactive
ResponsivenessNo issues