Gandr TTS
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GANDR_API_KEY | Yes | Your Gandr API key (e.g., gnd_...) |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| synthesizeA | Render text to speech. Returns the WAV audio base64-encoded. voice: one of gandr-ava, gandr-dane, gandr-jenny, gandr-leo, gandr-lewis, gandr-mia. language: a two-letter code, call list_languages for the 23 supported. Any voice can speak any of them. temperature: 0.1-1.2 pitch range (omit for the tuned default). cfg_weight: 0.2-1.0 pacing. sample_rate: 8000-48000. |
| list_voicesA | List the available Gandr voices with their ids. |
| list_languagesA | List the language codes synthesize accepts, with their names. |
| get_usageA | Characters used vs quota for the configured API key. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: synthesize for TTS, list_voices for voice metadata, list_languages for language metadata, and get_usage for account status. No two tools overlap in function.
Tool names are lowercase with underscores and mostly follow a verb_noun pattern (list_voices, list_languages, get_usage), but synthesize is a bare verb, which is a minor deviation from the pattern.
With four tools, the server is well-scoped: one core operation, two metadata lookups, and one usage check. This is an ideal size for a TTS-focused server.
The tool surface covers the essential lifecycle for text-to-speech: the synthesis action, necessary resource discovery (voices/languages), and account monitoring. There are no obvious gaps or dead ends.