Skip to main content
Glama

Science Feeds

by io.github.pipeworx-io

Subscribe to Alerts

subscribe
Idempotent

Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = officer change), "polymarket_edge" (Polymarket↔Kalshi cross-venue mispricings — params:{topic:"fed"}), "fred_series" (new FRED observations — params:{series_id:"UNRATE"}). Delivery channels: feed (always on — pull via recent_alerts or GET registry.pipeworx.io/alerts.json), and optionally email (set delivery:{email:"you@x.com"}) or sms (delivery:{sms:"+15551234567"} — phone must be verified at /account first; 10/day cap).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesSubscription type.
paramsYesType-specific filter. sec_8k: {ticker:"AAPL", items?:["5.02","1.01"]}. polymarket_edge: {topic:"fed", min_spread_bps?:500}. fred_series: {series_id:"UNRATE"}. patent_grant: {applicant:"Apple Inc."}. clinical_trial: {sponsor?:"Pfizer", condition?:"lung cancer", phase?:"PHASE3"} (sponsor or condition required).
deliveryNoOptional delivery channels in addition to the always-on persistent feed. {email:"you@x.com"} sends a templated alert per fired event. {sms:"+15551234567"} sends an SMS per event — must match the verified phone on the caller's account (verify at https://pipeworx.io/account first; 10/day cap). {webhook:"https://..."} POSTs each event JSON to your endpoint, HMAC-signed — the response includes delivery.webhook_secret (whsec_…) ONCE; verify X-Pipeworx-Signature = sha256 HMAC of "<X-Pipeworx-Timestamp>.<raw body>". Auto-disabled after 10 consecutive failing runs.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already provide idempotentHint and non-destructive, but description adds critical context: OAuth requirement, delivery channels with HMAC signing, auto-disable after 10 failures, and return value. Goes well beyond annotations.

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 but well-structured, front-loading the main purpose and then detailing types and delivery. Every sentence adds value; could be slightly more concise but still effective.

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 complex tool with multiple subscription types and delivery channels, the description covers prerequisites (OAuth), return value, type parameters, delivery constraints, and failure behavior. No output schema, so description fulfills the need comprehensively.

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 parameters have descriptions. However, the description adds substantial value by explaining type-specific parameters with examples and clarifying delivery options, including constraints not in schema.

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 clearly states 'Create a proactive monitoring subscription to a live-data event stream' and 'Returns the new subscription id'. It distinguishes from siblings like list_subscriptions and unsubscribe by focusing on creation.

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

Usage Guidelines4/5

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

Explicitly requires Pipeworx OAuth account and details delivery constraints (phone verification, 10/day cap). Provides context on supported types and parameters, but does not explicitly state when to use this tool versus alternatives.

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

All Science Feeds toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Several tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta (currently identical), ask_pipeworx_grounded, deep_research, and validate_claim all route questions to data, while the six polymarket_* tools blur edge-finding, arbitrage, and fill-risk. ai_visibility_check and scan_competitor_ai_presence also overlap, with the latter wrapping the former.

Naming Consistency3/5

All names are snake_case and readable, with clear families like polymarket_*, ask_pipeworx*, and list_*. However, conventions mix verb-first names (resolve_entity, read_feed) with noun-first names (entity_profile, pipeworx_trending, recent_alerts, deep_research), so no single pattern dominates.

Tool Count2/5

34 tools is heavy for any server, but the real issue is scope sprawl: science feeds, a universal data router, prediction-market analysis, memory, subscriptions, AI-visibility checks, and npm scanning each form a mini-server. The count is not defensible for the 'Science Feeds' purpose and would be better split into several focused servers.

Completeness2/5

There is no coherent domain to assess completeness against—'Science Feeds' describes only 3 of 34 tools. Individual clusters are partially complete (subscriptions have subscribe/list/unsubscribe/recent_alerts, memory has remember/recall/forget), but the overall surface is a grab-bag of features from unrelated products, with obvious gaps in each (e.g., no way to update a subscription, no direct access to specific data packs except through the router).

Resources