loreroom
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_recent_contextA | 撈回最近 N 小時的 Telegram 對話（含時間、發出方、內容；雙向都有）。當你缺乏上下文、或使用者提到『剛剛/今天/昨天/最近』時，務必優先呼叫本工具還原脈絡。 |
| search_tg_historyA | 用關鍵字全文搜尋過去所有 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 2 tools
The two tools have clearly distinct purposes: one retrieves recent context by time, the other searches history by keywords. There is no overlap.
Both tools use consistent snake_case naming with a verb_noun pattern (get_recent_context, search_tg_history), making them predictable.
With only 2 tools, the server feels thin for its intended purpose of Telegram history retrieval, but it is borderline as it covers two essential retrieval methods.
The tool set covers time-based and keyword-based retrieval, but lacks other potentially useful operations like retrieving by user or date range, leaving notable gaps.