tgreader-mcp
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
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 |
|---|---|
| list_channelsA | List Telegram channels the account is subscribed to. Args: account: Account name (default: configured default account). search: Optional RegExp pattern to filter by channel title or username (max 200 chars). limit: Maximum channels to return (default 100, max 500). Returns JSON: {"count": N, "channels": [{"id", "title", "username", "type", "participants_count"}]} |
| read_messagesA | Read messages from a Telegram channel. Args: channel: Channel @username or numeric ID. account: Account name (default: configured default account). limit: Max messages when offset_date is None (default 20, max 1000). offset_date: ISO 8601 datetime — read all messages before this date (capped at 1000). search: Optional RegExp pattern to filter message text (max 200 chars). Returns JSON: {"count": N, "channel": {"id", "title", "username"}, "messages": [{"id", "date", "text", "views", "reactions", "media_type", "link"}]} |
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 are completely distinct: one lists channels, the other reads messages from a specific channel. There is no overlap or ambiguity.
Both tool names follow the verb_noun pattern ('list_channels', 'read_messages'), making them predictable and easy to understand.
With only 2 tools, the set is minimal but well-suited for a read-only Telegram client. It could benefit from additional tools like a channel info getter, but it is not overly sparse.
The tools cover the core read operations: listing channels and reading messages. Missing features like retrieving a single channel's details or searching across channels are minor gaps for a focused read-only tool.