Skip to main content
Glama

Sports 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.

TDQS

A4.7/5.0
Behavior5/5

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

Description discloses important behaviors beyond annotations: account requirements, SMS verification and daily cap, always-on feed, webhook HMAC signing and auto-disable after 10 failures, and that the webhook signing secret is revealed only once. No contradiction with annotations (readOnlyHint false, idempotentHint true).

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 dense but well-structured, front-loading the core purpose and then elaborating on types and delivery. It is longer than ideal, but every section adds necessary detail for a tool with nested parameters and multiple variants, so the length is justified.

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?

Given the tool's complexity (3 params, nested objects, multiple subscription types, delivery channels, no output schema), the description covers all essential usage aspects: supported types, parameter examples, delivery options, authentication requirements, limits, and return value. It is complete enough to guide correct invocation.

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?

Although schema coverage is 100%, the description adds substantial meaning for each parameter: it explains the type enum with concrete examples (e.g., sec_8k items, polymarket_edge topic), elaborates delivery sub-parameters with email, SMS, and webhook specifics, including verification requirements and URL restrictions. This goes far beyond the schema's field descriptions.

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 identifies the tool's purpose: 'Create a proactive monitoring subscription to a live-data event stream.' It names the resource and verb, mentions the return value (subscription id), and distinguishes it from siblings like unsubscribe, list_subscriptions, and recent_alerts 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?

It explains when to use the tool (to subscribe to alert types) and provides context for prerequisites (OAuth account, verified phone for SMS) and delivery options (feed, email, SMS). However, it does not explicitly mention when not to use it or name alternatives like recent_alerts for pulling the feed, though it references that channel implicitly.

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

All Sports 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.6/5.0
Disambiguation2/5

Several tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded differ only in mode, and the polymarket_* cluster (polymarket_edges, polymarket_edge_tracker, polymarket_arbitrage, polymarket_fill_risk, polymarket_kalshi_spread) all target prediction-market analysis with fuzzy boundaries. The presence of ai_visibility_check and scan_competitor_ai_presence, plus discover_tools and suggest_questions, adds further ambiguity about which tool to select first.

Naming Consistency3/5

Names are all snake_case but follow mixed conventions: verb_noun (list_feeds, read_feed, fetch_feed, validate_claim) coexists with noun_phrase (entity_profile, recent_changes, polymarket_edges) and prefix-grouped names (ask_pipeworx*, polymarket_*). While subgroups are internally consistent, the overall set lacks a unified pattern, though it remains readable.

Tool Count2/5

34 tools is well above the 25+ threshold for too many, and the count is especially inappropriate for a server named 'Sports Feeds' — most tools are generic data-research or meta-tools (subscriptions, memory, feedback, discovery) unrelated to sports feeds. The bloat suggests the server is actually a broad Pipeworx gateway, not a focused sports feeder.

Completeness2/5

For a sports-feeds server, only list_feeds, read_feed, and fetch_feed address the core domain, and there is no feed search, categorization beyond a simple list, or sports-specific analytics. While the general research surface (SEC, FDA, economics, prediction markets) is fairly comprehensive, it is misaligned with the stated server purpose, leaving the actual sports-feed functionality thin and with obvious gaps.

Resources