Skip to main content
Glama

Security 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.5/5.0
Behavior4/5

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

Annotations declare idempotentHint=true and not readOnly. Description confirms creation behavior, mentions OAuth requirement, SMS cap, webhook signing secret delivered once, and auto-disable on failures. Does not explicitly state idempotency but does not contradict 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?

Single dense paragraph front-loads purpose and requirements. Could be more structured with bullets, but every sentence adds value. Not verbose.

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 3 params, 2 required, nested objects, and no output schema, the description covers all critical aspects: returns subscription id, type-specific params, delivery details with constraints, required account type. Agent has sufficient info to use correctly.

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?

Schema coverage is 100% and description adds extensive real-world examples for each type (e.g., sec_8k with item codes, fred_series with series_id). For delivery, it explains webhook HMAC signing and auto-disable conditions, far beyond bare 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 the verb 'Create' and resource 'proactive monitoring subscription' with specific outcome 'Returns the new subscription id'. It distinguishes from siblings like unsubscribe and list_subscriptions by framing it as creation of a live-data event stream subscription.

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?

Provides explicit requirements: Pipeworx OAuth account, supported types with examples, delivery options. Lacks explicit 'when not to use' but context from siblings and the detailed type descriptions make usage clear.

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

All Security 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.9/5.0
Disambiguation2/5

The ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded trio creates real selection ambiguity — beta is currently identical to the stable router, and grounded shares the same routing with an added evidence step. Polymarket tools also overlap (polymarket_edges vs polymarket_arbitrage both surface structural arbitrage), and entity_profile/recent_changes both pull filings and news.

Naming Consistency4/5

Most tools follow a snake_case verb_noun pattern (resolve_entity, list_feeds, validate_claim, compare_entities). Minor deviations exist — bare verbs (remember, recall, forget, subscribe, unsubscribe) and noun-first names (entity_profile, recent_changes, pipeworx_trending) — but the overall convention is consistent and readable.

Tool Count2/5

34 tools is excessive for a server nominally named 'Security Feeds' — only three tools actually relate to security feeds. Even as a broad data-research platform, the surface feels bloated with five near-exclusive Polymarket tools, three memory tools, and four subscription-lifecycle tools that could be consolidated.

Completeness4/5

For the actual domain revealed by the tools (data research, entity intelligence, prediction markets, subscriptions, feeds), coverage is strong: resolution, profiles, changes, comparison, claim verification, memory CRUD, subscription lifecycle, and feed operations are all present. Minor gaps include no subscription-update tool and no direct feed-search tool, but the ask_pipeworx router compensates.

Resources