ntfy-notify
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NTFY_TOKEN | No | Bearer token for protected / self-hosted topics. | |
| NTFY_TOPIC | Yes | Your long, random topic. Never hardcoded. | |
| NTFY_BASE_URL | No | Set to your own host if self-hosting. | https://ntfy.sh |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_notificationA | Send a push notification to the configured ntfy topic (your phone). Args: message: The notification body text. title: Optional bold title shown above the message. priority: One of min, low, default, high, urgent (or "1".."5"). Anything unrecognized falls back to "default". tags: Comma-separated emoji shortcodes, e.g. "tada,computer". click_url: Optional URL opened when the notification is tapped. Returns: A status string starting with "OK:" on success or "FAILED:" on error. |
| send_job_alertA | Send a job-search inbox-sweep summary with sensible defaults. Thin wrapper around send_notification: title "Job sweep", high priority, a briefcase tag. Intended for the daily job-inbox-sweep task. Args: summary: The summary text to push to your phone. Returns: A status string starting with "OK:" on success or "FAILED:" on error. |
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 clear, distinct purposes: send_notification for general push notifications and send_job_alert as a specialized wrapper for job search alerts. No overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern (send_job_alert, send_notification), making them predictable and intuitive.
With 2 tools, the set is minimal but well-justified: a general notification tool and a convenience wrapper for a common use case. A few more specific wrappers could be added, but current count is appropriate for the server's focused purpose.
The server's purpose is to send push notifications, and it provides both a general-purpose tool and a task-specific shortcut. There are no obvious gaps for the intended functionality.