Skip to main content
Glama

Climate 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.7/5.0
Behavior5/5

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

Annotations indicate a write (readOnlyHint=false) but no destruction. The description details subscription creation, return of id, OAuth requirement, as well as delivery nuances: email/SMS caps, webhook HMAC signing secret returned once, auto-disable after 10 failures. This 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 dense but well-organized, front-loading the main purpose and then detailing types and delivery. Every sentence adds value, though slightly verbose for the length.

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, 5 enum types, multi-channel delivery), the description captures all necessary context: type-specific params, delivery behavior, prerequisites, and return value. No output schema exists but the description adequately states the return.

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%, so baseline is 3. The description adds significant value by explaining each type's parameters (e.g., sec_8k item codes, polymarket_edge topic, fred_series series_id) and delivery object specifics (phone verification, email pattern, webhook HMAC and auto-disable).

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 explicitly states 'Create a proactive monitoring subscription to a live-data event stream' and notes it returns a subscription id. It clearly distinguishes from sibling tools like 'unsubscribe' and 'list_subscriptions' by specifying creation behavior.

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?

The description provides clear context: requires Pipeworx OAuth account, cannot be used by anonymous/BYO, lists supported types and delivery channels. It implicitly discourages use without an account but lacks explicit when-not-to-use or alternatives.

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

All Climate 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
Disambiguation3/5

Most tools have clearly distinct purposes with thorough descriptions, but ask_pipeworx_beta is currently identical to ask_pipeworx, and the five polymarket_* tools plus three ask_pipeworx variants form overlapping clusters that could cause misselection without careful reading.

Naming Consistency3/5

Names fall into recognizable families (list_*, read_*, fetch_*, polymarket_*, ask_pipeworx_*), but conventions are mixed: bare verbs like remember/forget, noun phrases like entity_profile/recent_alerts, and product-prefixed names. Predictable within families but inconsistent across the full set.

Tool Count2/5

34 tools far exceeds the 25+ threshold and the typical well-scoped server. The bulk of tools—Pipeworx data access, Polymarket analysis, memory, subscriptions—go far beyond what a 'Climate Feeds' server name implies, making the set feel bloated and unfocused.

Completeness4/5

For its actual (much broader-than-named) scope, the surface is remarkably complete: query, grounded verification, research, comparison, entity resolution, memory, subscriptions, feedback, and discovery all exist. Minor gaps remain—subscriptions cannot monitor arbitrary RSS feeds, and there is no update operation for subscriptions.

Resources