AivisSpeech MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| aivis-speech-synthesisD | – |
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 'aivis-speech-synthesis' stands alone with a distinct purpose, so agents cannot misselect among multiple options.
A single tool inherently has consistent naming, as there are no other tools to compare it against. The name 'aivis-speech-synthesis' follows a clear pattern of domain-specific naming, and no inconsistencies can arise from a set of one.
A single tool for a speech synthesis server is too few for typical use cases, as it lacks essential operations like configuration, status checks, or batch processing. This minimal scope limits functionality and suggests an incomplete or overly simplistic implementation for the domain.
The tool set is severely incomplete for a speech synthesis domain, offering only synthesis without any supporting operations like listing voices, adjusting parameters, checking synthesis status, or handling errors. This creates significant gaps that will likely cause agent failures in real-world scenarios.