it-digest
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTHROPIC_API_KEY | No | API key for Anthropic, needed for the make_digest phase 2 pipeline. |
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 |
|---|---|
| fetch_latestA | Fetch the latest articles from all configured RSS feeds and store them (duplicates are skipped). Use when the user wants to refresh the archive or asks about the newest articles. |
| search_archiveA | Search stored articles by keyword (matches title or summary). Use when the user asks about a specific topic from the archive. |
| get_articles_for_digestA | Return raw article data (title, URL, source, summary) from the last
|
| make_digestA | Build a ready-made markdown digest of the most relevant articles
from the last |
| list_sourcesA | List the feeds the digest currently aggregates, with the number of stored articles per source. Reports whether the app runs on bundled default feeds (feeds.txt is empty) or the user's own selection. |
| add_sourceA | Validate and add a new RSS/Atom feed to feeds.txt. Use when the user wants to follow a new source. The feed is downloaded and parsed first - invalid or dead URLs are rejected, nothing is written. While feeds.txt is empty the app runs on bundled default feeds. When adding the user's FIRST own feed, ask them once whether to keep the defaults too (then call this with keep_defaults=True) or start fresh with only their own sources. Do not ask again once feeds.txt has entries. |
| remove_sourceA | Remove a feed from feeds.txt. Use when the user no longer wants a source. Already stored articles from that source stay in the archive. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| setup_sources | Reusable prompt: find, validate and add quality feeds for a topic. |
| daily_digest | Reusable prompt: refresh the archive and write a themed digest, optionally focused on one topic. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools have clearly distinct purposes: add_source vs remove_source are opposites, fetch_latest vs search_archive vs get_articles_for_digest each target different actions. The only slight ambiguity is between get_articles_for_digest and make_digest, but the latter is explicitly marked as not implemented and directs to the former.
All tool names follow the same verb_noun pattern in lowercase with underscores (add_source, remove_source, fetch_latest, search_archive, get_articles_for_digest, make_digest, list_sources). This is highly consistent and predictable.
With 7 tools, the set is well-scoped for an RSS digest server: source management (add, remove, list), content fetching, archive search, and digest creation. Each tool serves a distinct purpose without unnecessary bloat or missing essentials.
The core workflows are covered: source CRUD (add/remove/list), fetching latest articles, searching the archive, and retrieving articles for a digest. Minor gaps include lack of an update_source tool and the unimplemented make_digest, but the alternatives provided make the surface functional.