notification
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELEGRAM_CHAT_ID | Yes | Your Telegram chat ID where messages will be sent | |
| TELEGRAM_BOT_TOKEN | Yes | Your Telegram bot token from BotFather |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_notificationB | Send a text message notification to the user |
| check_notification_responseB | Check if the user has responded to a notification |
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 clearly distinct purposes: one sends a notification, the other checks for a response. There is no overlap or confusion between them.
Both tool names follow a consistent verb_noun pattern (send_notification, check_notification_response), using snake_case and clear action-object structure.
With only 2 tools, the set feels thin, but it is plausible for a narrowly scoped notification utility. It is not extreme, but on the low end of the typical range.
The pair covers sending a notification and checking for a response, which are the core operations. Missing features like canceling or resending are minor gaps that agents can work around.