MCP Simple AivisSpeech
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 |
|---|---|
| check_engine_statusB | Check if AivisSpeech engine is running |
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 tool's purpose is clearly distinct as it is the only one available.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name follows a clear verb_noun pattern (check_engine_status).
One tool is too few for a server named 'MCP Simple AivisSpeech', which implies speech-related functionality. The scope appears thin, lacking basic operations like text-to-speech or speech-to-text that would be expected in this domain.
The tool set is severely incomplete for a speech-related server. It only checks engine status, missing core functionalities such as generating speech, processing audio, or managing speech settings, which are essential for the apparent purpose.