Dotiphant
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_chatsA | List archived Telegram chats with chat id, kind, last activity and message count, most recent first. Use it to find a chat id or to see when a chat was last active. query: part of a chat title or username. kind: private, group, channel or bot. active_since: only chats with messages since then, like "24h", "7d" or "2026-09-01". |
| search_messagesA | Keyword search over all archived messages and file names, newest first, grouped by chat. Returns message ids to open with get_messages(around_message_id=...). query: 1 to 3 distinctive words; every word must match, as a prefix ("audit" also finds "audits"). If no message has all words, messages with any of them are returned. Use "quoted phrases" and OR for alternatives (launch OR release). Not semantic: search for words the messages would contain, not for the question. chat: chat id, @username or part of a title. sender: part of a sender name or username. since/until: "24h", "7d", "2026-09-01" or an ISO timestamp. media: only messages with an attachment: "files" (photos, videos, documents, voice, audio), "any", or one of photo, video, document, voice, audio, sticker, poll, link. |
| get_messagesA | Read one chat in chronological order, one line per message ([ref], #id, date UTC, sender, text). Without since/around_message_id you get the newest |
| recent_activityA | What happened recently across chats, most recent first: per chat the number of new messages, the latest few, and a flag on chats waiting for the user's reply. Use for "what's new", "what did I miss" and "who am I owing an answer". since: "24h", "7d", "2026-09-01". chats: limit to these chats. per_chat: messages shown per chat (max 20). kind: only private chats, groups, channels or bots. |
| chat_infoB | Details of one chat: kind, members, forum topics, most active participants with usernames, and archive coverage (first and last message). |
| refreshA | Fetch new messages from Telegram into the archive (all chats, or one chat), then wait up to wait_seconds (max 300) for it to finish. Refreshing one chat also picks up edits to its recent messages. Never sends anything to Telegram. |
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
Each tool has a distinct read-only role: listing chats, detailing one chat, searching messages, reading a chat, summarizing recent activity, and syncing the archive. There is minor overlap between list_chats, chat_info, and recent_activity, but their descriptions make the boundaries clear.
All names use consistent lowercase snake_case, making the set readable. However, the verb_noun pattern is only followed by list_chats, search_messages, and get_messages, while chat_info, recent_activity, and refresh deviate.
Six tools is well-scoped for a read-only Telegram archive browser, with each tool covering a distinct workflow. No tool feels redundant or missing from the core set.
The surface covers chat discovery, message search, chronological reading with paging, recent activity summaries, chat metadata, and archive refresh. For a read-only archive, there are no obvious dead ends or missing lifecycle operations.