ai-news
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_trending_newsA | Aggregates real-time AI/tech news from multiple sources (HackerNews, Dev.to, Reddit, ArXiv, GitHub Trending, GeekNews, Lobsters) with 1-hour caching. Reads from Supabase cache when available, falls back to local file cache. |
| get_top_picksB | Returns top N most relevant items for AI engineers, scored by source reputation (HN/Reddit > ArXiv > others) plus item score. Each item includes a one-liner 'why it matters' and optional try_url. |
| get_repo_quickstartA | Fetches a GitHub repo's metadata (stars, description, language, topics) and extracts install commands and a quickstart code block from its README. |
| get_paper_briefA | Fetches an ArXiv paper's title, authors, abstract, and submission date. Searches Papers With Code and GitHub for associated code repositories. |
| search_todayA | Search today's cached news by keyword query. Matches against title and summary, scores by word match count × item score. Returns top results. |
| get_new_sinceA | Queries Supabase for all cache rows created after a given ISO timestamp. Returns deduplicated news items sorted newest first. Requires Supabase connection. |
| get_topic_suggestionsA | Suggests blog topic ideas based on trending news, tailored per project (potenlab, treesoop, hanguljobs) and filtered against already-used topics. |
| check_cacheA | Check the current state of the news cache — Supabase connection status, whether local/Supabase cache exists, how old it is, and how many items per source. |
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 8 tools
Most tools have clearly distinct targets: cache diagnostics, repo quickstart, paper brief, and topic suggestions don't overlap with anything. There is mild friction between get_trending_news and get_top_picks (both return news, one raw/aggregated and one ranked), and between search_today and get_new_since (both query the same cache, differentiated only by keyword vs. timestamp filter), but the descriptions make the boundaries recoverable.
All eight tools use snake_case verb_noun form (get_*, search_*, check_*), with no camelCase or bare nouns mixed in. The verb choice is predictable and informative: get_ for retrieval, search_ for querying, check_ for diagnostics.
Eight tools is well within the sweet spot for a news aggregation server, and each one maps to a distinct step: ingest, cache introspection, ranking, keyword search, delta fetch, and two enrichment tools plus topic ideation. Nothing feels padded or redundant at the count level.
The surface covers the core lifecycle: fetch news, inspect cache freshness, rank, search, delta-fetch, and enrich repos/papers, with an ideation tool on top. Minor gaps remain — there's no cache refresh/clear operation despite check_cache exposing state, no way to record a topic as 'used' even though suggestions filter against used topics, and no tool to retrieve a single article's full detail by id.