Skip to main content
Glama
norrietaylor

io.github.norrietaylor/distillery-mcp

Official
by norrietaylor

distillery_watch

List, add, or remove RSS and GitHub feed sources to control which content gets monitored.

Instructions

Manage monitored feed sources for ambient intelligence.

USE WHEN: listing, adding, or removing RSS/GitHub feed sources that Distillery polls for new content.

PARAMS:

  • action (str, required): Operation to perform. Valid: [list, add, remove].

  • url (str, required for add/remove): Feed URL or GitHub owner/repo slug.

  • source_type (str, required for add): Feed type. Valid: [rss, github].

  • label (str, optional): Human-readable label for the source.

  • poll_interval_minutes (int, optional, default=60): Polling frequency in minutes.

  • trust_weight (float, optional, default=1.0): Source trust weight (0-1).

  • thresholds (object, optional): Per-source overrides for the global feeds.thresholds values. Mapping with optional float keys alert and/or digest in [0.0, 1.0] (when both set, digest <= alert). When omitted, the global cutoffs apply (pre-existing behaviour). Use this to raise the bar for noisy aggregators (HN/Lobsters/Reddit) since trust_weight only attenuates downward.

  • sync_history (bool, optional, default=false): When true and source_type is "github", kicks off an async background import of historical issues/PRs (returns immediately with job_id; use distillery_sync_status to check progress).

  • purge (bool, optional, default=false): When true and action is "remove", archives all entries from the removed source (soft-delete). Returns the count of archived entries in purged_entries.

  • probe (bool, optional, default=true): When adding, lightly probe the URL for reachability (HEAD with GET fallback, short timeout). Returns an INVALID_PARAMS error (with details.probe_failed=true) if the probe fails.

  • force (bool, optional, default=false): When adding, persist the source even if the reachability probe fails (useful for sites that block HEAD but work via the poller).

  • mode (str, optional, github only): Which content-bearing surface to poll. Valid: [releases, events]. Defaults to "releases" (one body-bearing entry per release). "events" is the opt-in contentless firehose.

RETURNS (success): { sources: list, count: int } (list) or { added: dict, sources: list, sync_job?: dict } (add) or { removed_url: str, removed: bool, sources: list, purged_entries?: int } (remove) RETURNS (error): { error: true, code: "INVALID_PARAMS" | "CONFLICT" | "INTERNAL", message: "..." }

RELATED: distillery_configure (to adjust feed thresholds), distillery_store_batch (for bulk entry ingestion)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo
modeNo
forceNo
labelNo
probeNo
purgeNo
actionYes
thresholdsNo
source_typeNo
sync_historyNo
trust_weightNo
poll_interval_minutesNo
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden and does so thoroughly. It discloses return payloads for success (list/add/remove) and error codes with structure, explains async behavior (sync_history returns immediately with job_id), soft-delete semantics (purge archives entries), probe behavior (HEAD with GET fallback, INVALID_PARAMS on failure), and even the thresholds constraint (digest <= alert). No contradictions exist.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long due to the 12 parameters and rich behavioral detail, but it is well-organized with clear sections (USE WHEN, PARAMS, RETURNS, RELATED). Every sentence earns its place, though a few lines (e.g., thresholds rationale) could be tighter without losing value. Still, it remains efficient relative to the complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 12 params and no output schema, the description covers everything an agent needs: full return shapes for all actions, error handling, per-parameter constraints, async job linkage, and cross-references to related tools. No information is missing for correct invocation, making it complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has zero property descriptions, so the description must compensate entirely. It does: every parameter (action, url, source_type, label, poll_interval_minutes, trust_weight, thresholds, sync_history, purge, probe, force, mode) gets a meaning, valid values, defaults, and often context (e.g., why use thresholds for noisy aggregators). This is far beyond a baseline, fully bridging the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource: 'Manage monitored feed sources' and immediately narrows scope with 'USE WHEN: listing, adding, or removing RSS/GitHub feed sources'. It distinguishes itself from siblings by mentioning distillery_configure (thresholds) and distillery_store_batch (bulk ingestion) in RELATED, making the tool's unique role unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'USE WHEN' section defines the exact conditions for invoking this tool. It also provides exclusions and alternatives: distillery_configure for threshold adjustment, distillery_store_batch for bulk ingestion, and distillery_sync_status for checking background sync progress. The criterion for choosing this tool over siblings is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/norrietaylor/distillery'

If you have feedback or need assistance with the MCP directory API, please join our Discord server