Sound Effects MCP
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 |
|---|---|
| play-sound-effectB | 効果音を再生します（完了音、ニュータイプ音、エラー音） |
| list-sound-effectsB | 利用可能な効果音の一覧を表示します |
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 clearly distinct purposes: one lists available sound effects, and the other plays a selected sound effect. There is no overlap or ambiguity between these functions, making it easy for an agent to choose the correct tool based on the task.
Both tool names follow a consistent verb-noun pattern using kebab-case (list-sound-effects, play-sound-effect). This predictable naming scheme enhances readability and makes the tool set coherent and easy to understand.
With only 2 tools, the set feels thin for a sound effects server. While the tools cover basic listing and playback, there are likely missing operations such as searching, filtering, or managing sound effects (e.g., upload, delete). The count is too low for a comprehensive sound effects domain.
The tool set is severely incomplete for a sound effects domain. It lacks essential operations like searching for specific sounds, uploading new effects, deleting or organizing effects, and controlling playback (e.g., stop, pause, volume). Agents will face dead ends when trying to perform common sound management tasks.