peacelingo-stt-bench
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROQ_API_KEY | No | API key for Groq. Can also be provided in ~/.config/peacelingo/groq.env; the environment variable takes precedence. | |
| SONIOX_API_KEY | No | API key for Soniox. Can also be provided in ~/.config/peacelingo/soniox.env (one line SONIOX_API_KEY=...); the environment variable takes precedence. | |
| ASSEMBLYAI_API_KEY | No | API key for AssemblyAI. Can also be provided in ~/.config/peacelingo/assemblyai.env; the environment variable takes precedence. | |
| STT_BENCH_DAILY_CAP | No | Maximum number of provider calls allowed per day (default 50). | 50 |
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 |
|---|---|
| compare_sttA | Send one short clip (wav/mp3/m4a, up to 30 s and 10 MB, from the repo's clips/
folder only; URLs are refused) to the configured speech-to-text providers and
return, per provider: transcript (max 2000 chars), CER, WER, latency and estimated
cost. |
| list_providersA | List the providers, their model, whether a key is configured (never the key), the hourly price and its source, and how many provider calls are left today. |
| estimate_costA | Estimate the cost in USD of transcribing |
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 3 tools
The three tools have largely distinct purposes: list_providers is introspection, estimate_cost is a pure price calculation, and compare_stt runs an actual benchmark. There is minor overlap since compare_stt also returns estimated cost per provider, but the descriptions make clear it requires a real clip while estimate_cost is a duration-only calculation.
All three names follow a clean verb_noun snake_case pattern (compare_stt, list_providers, estimate_cost) with no convention mixing. The abbreviation 'stt' is consistent with the server domain.
Three tools is on the lean side but each earns its place for a focused STT benchmarking server (run comparison, inspect providers, estimate cost). It is slightly thin but well-scoped rather than padded.
Core workflows are covered, but notable gaps exist: there is no tool to list available clips in the repo, no way to retrieve or persist past benchmark results, and no configuration/key management surface. Agents can work around these but the surface feels incomplete for a benchmark tool.