Skip to main content
Glama

Eodhd

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

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

Discloses auth requirement, persistence, delivery limits (10/day SMS), webhook auto-disable after 10 failures, one-time signing secret. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence adds value; front-loaded with purpose, then types and delivery. No fluff, well-organized.

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?

Covers all 5 types with detailed params, delivery options, auth requirements, and limits. Output schema not needed as tool returns id and webhook secret mentioned.

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?

Adds extensive examples and constraints for each type and delivery channel beyond schema descriptions, e.g., ticker+items for sec_8k, topic for polymarket_edge, phone verification for SMS, webhook signing details.

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?

Specific verb 'create' with clear resource 'subscription'. Distinguishes from siblings like list_subscriptions, unsubscribe, recent_alerts.

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?

States requirement for Pipeworx OAuth account, indicates when not to use (anonymous/BYO cannot persist), and suggests pull alternatives (recent_alerts, GET endpoint). Lacks explicit comparison to other tools but provides sufficient usage context.

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

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

Multiple tool clusters overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route research questions; polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, and bet_research all hunt prediction-market edges; ai_visibility_check and scan_competitor_ai_presence do nearly the same job. The verbose descriptions help, but an agent would still struggle to pick the right tool in these clusters.

Naming Consistency2/5

Everything is snake_case, but there is no coherent pattern: some names are verb_noun (compare_entities, validate_claim), some are bare verbs (remember, forget, recall), some are prefixed by domain (eodhd_*, pipeworx_*, polymarket_*, ai_visibility_*), and the Eodhd prefix clashes with the Pipeworx family. The conventions feel inherited from multiple unrelated codebases rather than a unified design.

Tool Count2/5

33 tools is already heavy for most servers, but the real problem is that only 2 tools (eodhd_eod_prices, eodhd_fundamentals) relate to the server's stated purpose. The other 31 span Pipeworx research, Polymarket betting, memory, subscriptions, feedback, llms.txt generation, and npm dependency checking — a massively over-scoped grab bag for a server named 'Eodhd'.

Completeness2/5

For the nominal EODHD domain the surface is severely incomplete: no splits, dividends, options, exchanges list, or other standard EODHD endpoints — just prices and fundamentals. As a general research/data platform it is broad rather than deep, mixing a decent question-answering core with unrelated one-off utilities, so no single coherent lifecycle is fully covered.

Resources