Telegram MCP 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 |
|---|---|
| get_unread_entitiesC | get entitites which have unread messages in it |
| get_unread_messagesC | get all unread messages from a given entity id |
| get_messagesC | Get messages limited by a count from an entity |
| get_entitiesB | Get all entities in the current session |
| get_entity_by_idC | Get an entity from the current session |
| send_messageC | Send a message to an entity with optional markup and reply |
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 6 tools
Most tools have distinct purposes, but there is some overlap between get_entities and get_unread_entities, as both retrieve entities, which could cause confusion about which to use. However, the descriptions clarify that one gets all entities and the other gets only those with unread messages, mitigating ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case, such as get_entities, send_message, and get_unread_messages. There are no deviations in naming conventions, making the set predictable and easy to understand.
With 6 tools, this server is well-scoped for managing Telegram sessions, covering key operations like retrieving entities, messages, and sending messages. The count is appropriate, avoiding bloat while providing essential functionality.
The toolset covers core messaging workflows, including reading and sending messages, but lacks operations for updating or deleting messages, which might be expected in a messaging domain. However, the provided tools handle the primary use cases effectively.