Skip to main content
Glama

Imf

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

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

The description discloses substantial behavioral traits beyond annotations: it requires a Pipeworx OAuth account, explains feed/email/SMS/webhook delivery channels, notes SMS verification and rate caps, and details webhook HMAC signing and auto-disable behavior. These details are not in the annotations and meaningfully guide correct invocation. No contradiction with 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 and front-loaded with the core purpose, and every section covers necessary aspects (auth, types, delivery). It is long but well-structured with commas and semicolons. A minor deduction because it repeats some schema details (e.g., SMS cap) and could be more scannable with bullet points, but overall it is efficient.

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 (5 subscription types, nested params, optional delivery object, no output schema), the description is thorough: it explains the return value (subscription id), enumerates all supported types with key parameters, details delivery options, and covers edge cases like webhook secret and auto-disable. No critical information appears missing.

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?

The input schema already has 100% coverage with detailed descriptions for all parameters. The description adds a few extra examples and clarifications (e.g., 'items:["5.02"] = officer change' and 'topic:"fed"'), but largely overlaps with schema content. This exceeds the baseline of 3 for high schema coverage, but does not warrant a 5 since much of the parameter guidance is already present.

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,' which includes a specific verb and resource. It clearly distinguishes from sibling tools like list_subscriptions and unsubscribe by focusing on creation and monitoring. It also states the return value, removing ambiguity.

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 for when to use the tool: for proactive monitoring subscriptions, and it mentions prerequisites like an OAuth account. It also hints at complementary tools by referencing 'pull via recent_alerts or GET registry.pipeworx.io/alerts.json.' However, it does not explicitly state when not to use it or name direct alternatives, so it falls short of a 5.

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

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

Several natural-language query tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, validate_claim) have heavily overlapping purposes, and ask_pipeworx_beta currently behaves identically to ask_pipeworx. The five Polymarket tools also have subtle boundaries, though the IMF, memory, and subscription clusters are clearly separated.

Naming Consistency4/5

Most tools follow a clean snake_case verb_noun pattern (get_data, resolve_entity, subscribe, compare_entities). Minor deviations exist: noun-first names like entity_profile and ai_visibility_check, brand-prefixed names like pipeworx_feedback and pipeworx_trending, and ask_pipeworx_beta using a suffix instead of an underscore.

Tool Count2/5

34 tools is well above the range that remains easily navigable, and the count is inflated by many meta-tools, overlapping query entry points, and five distinct Polymarket tools. The server is named Imf, yet it also carries npm dependency scanning, llms.txt generation, AI visibility checks, and prediction-market tooling, making the scope feel unfocused.

Completeness3/5

Subdomain lifecycles are reasonably covered: memory has remember/recall/forget, subscriptions have subscribe/list/unsubscribe/recent_alerts, and data access has discovery, lookup, grounding, and research paths. However, the overall domain is so broad that a complete surface is hard to define, and the IMF-specific portion is thin (only get_data, get_datasets, and search_indicators).

Resources