Skip to main content
Glama

Idf Events

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?

The description provides extensive behavioral context beyond annotations: it requires a Pipeworx OAuth account, details delivery channels (feed always on, optional email/SMS/webhook), rate limits (10/day for SMS), verification requirements for phone, webhook signing secret and auto-disable after 10 failing runs. Annotations are consistent (no contradiction), and the description adds significant value.

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 verbose but packed with essential information. It is front-loaded with the core purpose. Every sentence earns its place, but it could be slightly more concise for a 1.5-sentence summary. Still, it is well-structured and informative.

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 complexity (3 parameters, nested objects, no output schema), the description is thorough: it covers all subscription types, parameter details, delivery options, restrictions, and return value. It is entirely adequate for an agent to use the tool correctly without needing external documentation.

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 the description goes beyond the schema by providing detailed examples for each subscription type (e.g., sec_8k with items, polymarket_edge with topic, fred_series with series_id). It also explains delivery sub-parameters (email, sms, webhook) with usage restrictions. This adds significant meaning beyond the 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', the resource 'proactive monitoring subscription', and the action 'to a live-data event stream'. It also mentions the return value 'Returns the new subscription id', which distinguishes it from sibling tools like 'list_subscriptions' and 'unsubscribe'.

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 explicitly states when to use it ('Create a proactive monitoring subscription') and provides context for the types of event streams. It does not explicitly state when not to use it or mention alternatives, but the use case is clear and the description is sufficient for an agent to decide. A slight deduction for lacking explicit exclusions.

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

All Idf Events 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

Many tools have overlapping purposes (e.g., three ask_pipeworx variants, multiple Polymarket analysis tools, and several entity-focused tools). Agents may struggle to select the correct tool for tasks like querying data or analyzing prediction markets.

Naming Consistency4/5

All tool names use snake_case, and most follow a verb_noun pattern (e.g., ask_pipeworx, compare_entities). A few names like ai_visibility_check are slightly less conventional, but overall the naming is consistent.

Tool Count3/5

With 32 tools covering a broad range of data services, the count is on the high side but still manageable. However, the server name 'Idf Events' is misleading, as only one tool relates to events in Paris.

Completeness4/5

The tool set covers core workflows for the Pipeworx platform: data querying, research, comparisons, subscriptions, memory, and feedback. Minor gaps exist, but most user needs are addressed.

Resources