Skip to main content
Glama

Coingecko

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?

Beyond annotations, the description discloses that anonymous/BYO cannot persist, SMS has a 10/day cap, webhook auto-disables after 10 failures, and returns subscription id. 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 well-organized with front-loaded key info, but is somewhat lengthy due to detailed examples. However, complexity justifies 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 3 parameters (2 required), no output schema, the description covers purpose, parameter meanings, behavioral constraints, and side effects comprehensively. An agent can use it correctly.

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?

The description adds extensive meaning beyond the schema: explains type enum values with examples, details param structures for each type, and describes delivery channels with constraints. Schema coverage is 100%, but description enriches significantly.

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' and resource 'proactive monitoring subscription'. It lists supported event types and distinguishes from sibling tools like unsubscribe and list_subscriptions.

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 specifies when to use this tool (creating subscriptions), outlines requirements (Pipeworx OAuth), and gives examples for each type. It doesn't explicitly state when not to use, but the context is clear.

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

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

Several tools are near-duplicates or have heavily overlapping responsibilities (ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded, polymarket_arbitrage / polymarket_edges / polymarket_fill_risk, and ai_visibility_check / scan_competitor_ai_presence). The many meta/entry-point tools (discover_tools, suggest_questions, pipeworx_trending) also blur the boundary between discovery and execution.

Naming Consistency2/5

Tool names mix imperative verb-first patterns (get_coin, search_coins, validate_claim) with noun-phrase labels (bet_research, entity_profile, pipeworx_trending, polymarket_edge_tracker) and inconsistent prefixes. Snake_case is consistent, but the naming grammar and verb styles are not.

Tool Count2/5

35 tools is well past the comfortable range, and the count feels inflated by duplicate routing modes, overlapping polymarket scanners, and generic memory/meta utilities. A server nominally named Coingecko carries only 4 crypto tools while the overwhelming majority belong to unrelated domains.

Completeness2/5

As a CoinGecko server, the surface is severely incomplete: search/get/market/trending exist but historical prices, OHLC, exchanges, categories, and coin details are missing. As a broader data/prediction-market utility it is more expansive, but the lack of a coherent domain makes coverage impossible to assess as a single product.

Resources