telegram-commandcode
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELEGRAM_BOT_TOKEN | Yes | Bot token from @BotFather | |
| TELEGRAM_DEFAULT_CHAT_ID | No | Default target chat ID |
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 |
|---|---|
| telegram_send_messageA | Send a text message to a Telegram chat. Supports MarkdownV2 and HTML parse modes. Messages longer than 4096 characters are rejected by Telegram — split them first. |
| telegram_send_photoA | Send a photo via a public URL or an absolute local file path (max 10 MB for photos). |
| telegram_send_fileA | Send a document/file via an absolute local path or public URL (max 50 MB). Useful for build logs, diffs, screenshots and reports. |
| telegram_get_updatesA | Fetch recent incoming messages. By default only unseen updates are returned and acknowledged; pass offset: 0 to re-read the backlog. |
| telegram_healthA | Check that the bot token works: returns bot id, username and capabilities. |
| telegram_send_reactionA | Set an emoji reaction on a message (👀 working, ✅ done, ❌ failed). The bot must be a member of the chat. |
| telegram_download_fileA | Download a file from Telegram by file_id (max 20 MB via the Bot API) and return its local path. |
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 7 tools
Each tool targets a distinct action: three send variants are cleanly separated by payload type (text, photo, document) with explicit size limits, and get_updates/download_file/reaction/health have no overlap. An agent can pick the right tool from the names alone.
All tools share a consistent `telegram_` prefix and snake_case, with verb_noun forms for the action tools (send_message, get_updates, download_file). The only deviation is `telegram_health`, a noun phrase rather than a verb, but it remains readable and predictable.
Seven tools is well-scoped for a Telegram bot bridge: send, receive, download, react, and health-check. Nothing feels redundant or missing from a count perspective.
Core lifecycle is covered: outbound text/media, inbound updates, file download, reactions, and auth verification. Gaps exist around message management (edit, delete, reply/thread targeting) and chat introspection (list chats, get chat info), which agents may need for richer interactions.