Skip to main content
Glama

usgswater

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

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

The description goes well beyond annotations by disclosing auth requirements (anonymous/BYO cannot persist), phone verification, SMS cap, webhook auto-disable after 10 failures, and one-time signing secret. It does not contradict the idempotentHint annotation, though it could add more detail on idempotency behavior.

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 a single dense paragraph that stays on-topic. Every clause adds value (types, auth, channels). It is longer than the typical description but the complexity justifies it; no fluff.

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?

Given the tool's complexity (3 params, nested objects, 5 enum types, no output schema), the description covers purpose, return value, auth, all supported types, delivery options, and consumption path. It doesn't mention subscription limits or cancellation, but these are less critical and sibling tools cover them.

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%, providing baseline 3. The description adds concrete examples for each type (e.g., items:['5.02'] = officer change, topic:'fed') and delivery constraints (10/day SMS cap, phone verification), enriching parameter understanding beyond schema text.

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 opens with 'Create a proactive monitoring subscription to a live-data event stream,' a specific verb and resource. It clearly states the return value (new subscription id) and 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 Guidelines3/5

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

The description implies usage for ongoing monitoring ('proactive monitoring subscription', 'always on feed') and notes a prerequisite (OAuth account). However, it does not explicitly mention alternatives or when not to use subscribe, such as referencing list_subscriptions for viewing existing subscriptions.

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

All usgswater 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

A4/5.0
Disambiguation3/5

Several tools overlap: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all serve as query routers, with the beta variant currently identical to the stable one. However, most other tools have clearly distinct purposes (memory, subscriptions, prediction market analytics), and the detailed descriptions help differentiate them.

Naming Consistency4/5

All tool names use snake_case and are descriptive, with consistent domain prefixes like pipeworx_ for meta tools and polymarket_ for prediction markets. Some names mix noun-phrase and verb-noun patterns (e.g., ai_visibility_check vs. resolve_entity), but the overall style is predictable and readable.

Tool Count2/5

With 31 tools, the server exceeds the 25-tool threshold for a coherent set. While the broad scope (data querying, prediction markets, memory, subscriptions, AI visibility) justifies many tools, the sheer number creates cognitive load and makes selection harder for agents.

Completeness4/5

The tool surface is quite comprehensive for its domains: querying has ask_pipeworx, grounded answer, deep research, entity profiles, comparisons, and claim validation; prediction markets have research, arbitrage, edge tracking, and fill risk; memory and subscription lifecycles are covered. Minor gaps exist (e.g., no subscription update) but are workable.

Resources