play-sound-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 |
|---|---|
| play-local-soundB | ローカルのサウンドファイル（sound.mp3）をafplayで再生します。 |
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 confusion between tools. The single tool 'play-local-sound' has a clearly defined and distinct purpose.
A single tool inherently exhibits perfect naming consistency, as there are no other tools to compare against. The name 'play-local-sound' follows a clear verb_noun pattern.
A single tool is generally too few for a meaningful server scope, as it offers minimal functionality and limits agent capabilities. For a sound-playing server, basic operations like stop, pause, or list sounds might be expected.
The server is severely incomplete for a sound-playing domain. It only provides playback of a specific local file ('sound.mp3') with no ability to handle different files, control playback (e.g., stop, volume), or manage sound resources, creating significant gaps for agent workflows.