oai-tts
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OAI_TTS_MODEL | Yes | TTS 模型名称，例如 gpt-4o-mini-tts。用于 list_voices 查询 GET /v1/tts/voices?model={OAI_TTS_MODEL}。 | |
| OAI_TTS_VOICE | Yes | 默认音色 ID，例如 marin。text_to_speech 未指定 voice 时使用。 | |
| OAI_TTS_API_KEY | Yes | OpenAI 或 OpenAI 兼容 TTS 服务的 API Key。 | |
| OAI_TTS_BASE_URL | Yes | OpenAI 或 OpenAI 兼容 TTS 服务地址，例如 https://api.openai.com/v1。对 Base URL 自动规整：https://host 与 https://host/v1 均可。 | |
| URUSAI_API_TOKEN | No | 可选：Urusai 图床访问令牌。音频将上传至第三方并返回公开 URL。 | |
| URUSAI_UPLOAD_URL | No | 可选：上传端点，默认 https://api.urusai.cc/v1/upload；仅用于自建兼容上传服务或本机测试。 |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_voicesA | 获取当前 OAI_TTS_MODEL 的可用音色。优先调用 GET /v1/tts/voices?model=...；上游失败、超时或响应无效时自动返回内置 OpenAI 音色，并在结构化结果中标记 source=fallback。 |
| text_to_speechA | 调用 OpenAI 兼容 POST /v1/audio/speech 生成语音，并上传到 Urusai 文件托管服务。传入 instructions 可指定语气、情绪、节奏或风格；未指定 voice 时使用 OAI_TTS_VOICE；未指定 speed 时默认 1.25。成功后仅返回公开音频 URL。 |
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 2 tools
The two tools have entirely distinct purposes: list_voices enumerates available voices, while text_to_speech synthesizes audio and uploads it. There is no plausible way to confuse them, and the descriptions make the boundary explicit.
Both names use consistent snake_case, which is predictable. minor deviation: list_voices follows a verb_noun pattern while text_to_speech is a noun phrase (verb implied), so it is not a perfectly uniform convention.
With only two tools the surface is thin even for a narrowly scoped TTS server, which could reasonably expose model listing, voice preview, or audio retrieval operations. It is not a mismatch, but it sits at the borderline of minimal coverage.
The core lifecycle (discover voices, then synthesize speech) is covered, including fallback behavior and defaults for voice/speed. Missing secondary operations like previewing a voice or listing models are gaps agents can work around.