Skip to main content
Glama
Sign In

SignalPipe

by io.github.AbYousef739
OverviewDiscussionsAdmin

add_station

Add a feed for a product to monitor. Add 3-5; station CHOICE decides results.

Valid `platform`: `rss`, `hn`, `reddit`, `twitter_search` (the last only
routes outreach to X — it does NOT monitor X; X has no feed to read).

URL patterns:
  HN:      https://hnrss.org/newest?q=KEYWORDS
  Forum:   https://FORUM/latest.rss
  Q&A:     https://softwarerecs.stackexchange.com/feeds/tag/TAG

Reddit ends its RSS feeds on 13 November 2026: do not suggest Reddit feeds.
From that date they are refused, and existing ones return nothing.

Prefer a newest-first listing over a front page or hot listing: scoring
rewards recency heavily, and the first helpful reply is the one that gets read.

CHOOSING STATIONS — this matters more than any setting:
  * Prefer BROAD communities where buyers describe PROBLEMS, over narrow
    keyword or tool-name searches. Broad community feeds consistently
    produce the overwhelming majority of real leads; narrow keyword-search
    feeds frequently produce none at all.
  * Go where your buyer complains, not where your industry talks shop.
    Vendor/founder communities are dense with people BUILDING things like
    yours (correctly filtered out as sellers) and thin on buyers.
  * 3-5 well-chosen feeds beat 20. Every feed costs a fetch each cycle and
    sources rate-limit; more stations mainly buys you more noise.
  * Ask the user where their customers actually hang out and complain. They
    know; a guessed subreddit list is the most common cause of an empty queue.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product_id": "<product_id>",
      "name": "<name>",
      "platform": "<platform>"
    },
    "name": "add_station"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesA short name for the feed, such as "Help desk forum: latest".
keywordNoOptional note stored with the station, such as the search term the feed is built on. It does not filter posts.
rss_urlNoThe feed URL, needed for every platform except twitter_search. Hacker News: https://hnrss.org/newest?q=KEYWORDS; a forum: https://FORUM/latest.rss. Reddit ends its RSS feeds on 13 November 2026, and new Reddit feeds are refused from that date.
platformYesrss, hn, reddit or twitter_search. twitter_search only routes outreach to X; it does not read X.
product_idYesThe product this feed is for, from get_products.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / name / description
      Previous value: -"A short name for the feed, such as \"r/smallbusiness new\"."New value: +"A short name for the feed, such as \"Help desk forum: latest\"."
    • changedInput schema / properties / rss_url / description
      Previous value: -"The feed URL, needed for every platform except twitter_search. Reddit: https://www.reddit.com/r/SUBREDDIT/new/.rss, Hacker News: https://hnrss.org/newest?q=KEYWORDS."New value: +"The feed URL, needed for every platform except twitter_search. Hacker News: https://hnrss.org/newest?q=KEYWORDS; a forum: https://FORUM/latest.rss. Reddit ends its RSS feeds on 13 November 2026, and new Reddit feeds are refused from that date."
  2. Changed5 schema fields changed
    • addedInput schema / properties / keyword / description
      Added value: +"Optional note stored with the station, such as the search term the feed is built on. It does not filter posts."
    • addedInput schema / properties / name / description
      Added value: +"A short name for the feed, such as \"r/smallbusiness new\"."
    • addedInput schema / properties / platform / description
      Added value: +"rss, hn, reddit or twitter_search. twitter_search only routes outreach to X; it does not read X."
    • addedInput schema / properties / product_id / description
      Added value: +"The product this feed is for, from get_products."
    • addedInput schema / properties / rss_url / description
      Added value: +"The feed URL, needed for every platform except twitter_search. Reddit: https://www.reddit.com/r/SUBREDDIT/new/.rss, Hacker News: https://hnrss.org/newest?q=KEYWORDS."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare a non-readonly, non-idempotent, non-destructive write; the description adds real behavioral context: per-feed fetch cost each cycle, source rate-limiting, the Reddit RSS refusal after 13 Nov 2026, and that twitter_search does not actually read X. None of that is recoverable from annotations or schema.

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

Conciseness3/5

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

Front-loaded and clearly sectioned, but it is long for a single-tool definition and repeats itself: the 3-5 recommendation and the Reddit sunset date appear twice, and the Reddit warning duplicates the rss_url schema description. Useful content, but not tight.

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

Completeness4/5

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

Covers platform semantics, URL formats, selection strategy and the Reddit deprecation with no output schema to lean on. The only gap is what the call returns (e.g., a station id needed later for preview_station or update_station), which the agent must infer.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes beyond it by explaining that platform CHOICE changes results and by giving concrete URL construction patterns for HN, forum, and Q&A feeds, which the schema only gestures at.

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?

Opens with a specific verb and resource: 'Add a feed for a product to monitor.' That cleanly separates it from list_stations, update_station and remove_station, and the required product_id/platform framing tells the agent this creates a per-product source.

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 and opinionated: 'Add 3-5', 'station CHOICE decides results', prefer broad community feeds over narrow keyword searches, avoid vendor/founder communities, and 'do not suggest Reddit feeds'. It even names the escalation path (ask the user) and the consequence of ignoring the guidance (empty queue).

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

All SignalPipe toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources