Notifications MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_NOTIFICATION_SOUND | No | Choose from bundled sounds: cosmic, fairy, gentle, pleasant, retro, random. Default: gentle | gentle |
| MCP_NOTIFICATION_SOUND_PATH | No | Absolute path to your own MP3 file (overrides bundled sounds) |
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_notificationB | Play a notification sound to indicate task completion |
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 confusion or overlap between tools, as there are no other tools to compare it against. The tool's purpose is clearly defined and stands alone without ambiguity.
Since there is only one tool, naming consistency is inherently perfect; there are no other tool names to compare it to, and it follows a clear verb_noun pattern (play_notification). No inconsistencies can exist in a single-tool set.
A single tool for a 'Notifications MCP Server' feels thin and under-scoped, as it only provides a basic playback function without supporting operations like listing, creating, or managing notifications. This minimal set limits functionality and may not fully cover the expected domain of notifications.
The tool surface is severely incomplete for a notifications server, lacking essential operations such as creating, listing, updating, or deleting notifications. With only a playback tool, agents cannot perform basic CRUD or lifecycle management, leading to significant gaps in functionality.