edge-tts
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_speechC | Generate speech audio from text using Microsoft Edge TTS. Supports multi-role conversations and audio merging. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency. The tool name 'generate_speech' follows a clear verb_noun pattern, and there are no other tools to compare or create inconsistency with.
One tool is too few for most practical purposes, as it severely limits functionality. While it covers the core TTS generation, the server lacks tools for managing voices, configurations, or other related operations, making the scope feel incomplete and thin.
The server is severely incomplete for a TTS domain. It only provides speech generation without tools for listing available voices, adjusting speech parameters, or handling audio playback, leaving significant gaps that agents cannot work around effectively.