Skip to main content
Glama
myshli
by myshli

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_HOSTNoHost for the HTTP MCP server.127.0.0.1
MCP_PORTNoPort for the HTTP MCP server.8765
MCP_TOKENNoToken for the HTTP MCP server. Required when running with --http.
ARCHIVE_DBNoDatabase path. The systemd units set /var/lib/tg-archive/archive.db../archive.db
OPENAI_API_KEYYesOpenAI API key used for embeddings and semantic search.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_postsA

Hybrid keyword + semantic search over all archived posts.

query: natural-language or keyword query (any language; exact names like "Qwen3" or arXiv ids work too).
channels: restrict to these channel usernames.
since / until: ISO dates, e.g. "2026-09-01" (until is exclusive).
topics: any-of filter, values from list_topics().
kind: one post type from list_topics() (e.g. model-release, tool-release, paper, tutorial, humor).
hashtags: any-of filter on the author's own hashtags, e.g. ["text2video", "gaussian"] (very precise).
availability: any-of filter, e.g. ["open-weights", "code-only"] for things you can run locally.
Returns posts with date, channel, summary, topics, links, text snippet and permalink.
get_postA

Full text and metadata of one post (use after search_posts returns a snippet).

recentB

Posts from the last N days, newest first, optionally filtered by topics/channels. Good for "what happened this week in agents".

list_topicsB

Topics, post kinds and availability values (with descriptions and post counts), plus the author's most used hashtags. Call this to pick filters for search_posts.

statsB

Per-channel post counts, date range and enrichment progress.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 5 tools

Disambiguation4/5

get_post, list_topics, and stats are clearly distinct, and the descriptions even prescribe a workflow (list_topics → search_posts → get_post). The only mild overlap is between recent (time-windowed browsing) and search_posts (query-based retrieval), both returning filtered post lists, but the time-vs-query distinction is documented well enough to separate them.

Naming Consistency3/5

Two tools use the verb_noun pattern (get_post, list_topics) while the other three are bare nouns or adjectives (recent, stats, search_posts), and 'recent' in particular reads more like a parameter than a tool name. The set is still readable and unambiguous, but the convention is mixed.

Tool Count5/5

Five tools is a tight, well-scoped surface for a read-only archive server: discovery (list_topics, stats), retrieval (search_posts, recent), and expansion (get_post). Each tool has a clear job and none feels redundant.

Completeness4/5

The read-only lifecycle is covered end to end: find filters, search, browse recent, expand full text, and inspect corpus stats. Minor gaps remain — no explicit channel-enumeration tool (channels must be guessed or inferred from stats) and no pagination/offset control on search or recent results for large result sets.

Maintenance

ActivityMaintained
ResponsivenessNo issues