mcp-pushinator
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 a notification via the Pushinator API |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get-channels |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as sending notifications via the Pushinator API, making it distinct by default.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'send-notification' follows a clear verb-noun pattern, and there are no other tools to compare it against for inconsistency.
A single tool is generally too few for most server purposes, as it limits functionality and may indicate an incomplete or overly narrow scope. While it could be appropriate for a very simple notification service, it often feels thin and lacks the depth needed for typical agent workflows.
Inferring the domain as notification sending, the tool covers the core action of sending notifications. However, there are likely gaps such as managing notification settings, retrieving sent notifications, or handling errors, which could lead to incomplete workflows for agents.