Skip to main content
Glama

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:
  Reddit:  https://www.reddit.com/r/SUBREDDIT/new/.rss    <- use /new/
  HN:      https://hnrss.org/newest?q=KEYWORDS

Use `/new/.rss`, not the bare `/.rss`. Bare gives the HOT listing (popular,
already-answered posts); `/new/` gives fresh ones, and scoring rewards
recency heavily — 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesA short name for the feed, such as "r/smallbusiness new".
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. Reddit: https://www.reddit.com/r/SUBREDDIT/new/.rss, Hacker News: https://hnrss.org/newest?q=KEYWORDS.
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. 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."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-idempotent, non-destructive write, and the description adds behavior beyond them: every feed costs a fetch per cycle and sources rate-limit, and twitter_search behaves differently than its name suggests. It does not address duplicate/re-add behavior or error outcomes, which is a minor gap given idempotentHint=false.

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 scannable, but ~230 words with repeated editorializing: 'Add 3-5' is restated as '3-5 well-chosen feeds beat 20,' and 'prefer broad communities' overlaps with 'go where your buyer complains.' The CHOOSING STATIONS block is longer than the operational payload requires.

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?

With no output schema and 100% schema coverage, the description carries the platform and strategy burden well, including which platforms need a feed URL and which do not. It stops short of stating what a successful add returns or how duplicates are handled, but nothing essential to making the call is missing.

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, and the description adds real meaning on top: concrete URL patterns for Reddit and HN, the requirement to use /new/.rss rather than /.rss, and the clarification that twitter_search needs no rss_url and does not read X. It slightly duplicates schema text but the platform/URL semantics are genuinely extra.

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 precise verb+resource: 'Add a feed for a product to monitor,' immediately followed by scope guidance ('Add 3-5'). An agent can distinguish this from list_stations, remove_station, update_station and preview_station purely from the description.

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 when-and-how guidance: add 3-5 stations, valid platform values enumerated, and a hard exclusion — twitter_search 'only routes outreach to X; it does NOT monitor X.' It also gives selection criteria (broad communities over narrow keyword searches) and tells the agent to ask the user for sources.

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