MCP Notify 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 |
|---|---|
| send_notificationC | Send system notification with optional sound |
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 'send_notification' has a clear, distinct purpose that cannot be confused with any other tool in the set.
The tool name 'send_notification' follows a clear verb_noun pattern (send + notification). Since there is only one tool, consistency is inherently perfect with no deviations or mixed conventions to evaluate.
A single tool is too few for a server named 'MCP Notify Server', which suggests a broader notification domain. This minimal set feels thin and likely incomplete for typical notification workflows, such as managing notifications or checking statuses.
The tool surface is severely incomplete for a notification server. While 'send_notification' covers sending, there are obvious gaps like listing notifications, updating them, deleting them, or configuring notification settings, which agents would need for full functionality.