Skip to main content
Glama

Coingecko

by io.github.pipeworx-io

Polymarket Arbitrage

polymarket_arbitrage
Read-onlyIdempotent

Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a trending_scan of the top ~200 markets by weekly volume; pass event for the strongest per-event partition_check, or topic for a themed cross-event scan. event (recommended for a specific market): pass a Polymarket event slug like "fed-decision-may-2026" or "when-will-bitcoin-hit-150k"; walks child markets, checks date-axis / threshold-axis ordering AND computes the partition_check (sum of YES prices across mutually-exclusive legs — should ≈1; deviations >3pp emit a BUY/SELL EVERY LEG signal). topic (for cross-event scanning): pass a seed question like "Strait of Hormuz traffic returns to normal" or "Fed rate decision"; searches related events across the platform, flattens markets, runs the comparator on the union. Cross-event mode catches "...by May 31" vs "...by Jun 30" patterns that single-event misses. SEMANTIC ANCHOR: cross-event pairs require ≥0.30 Jaccard similarity on question tokens (prevents Powell-Fed-Pause being paired with Powell-DOJ-probe); skipped_low_similarity surfaces the rejected pair count. PARTITION FILTER: drops will-person-X / will-manager-Y / will-someone-else- placeholder slugs; partitions with >20% placeholder fraction return null arb signal. Response: opportunities[] (gap_pp, suggested_trade, reasoning, monotonicity violation context), and in event mode partition_check{sum_yes_prices, gap_from_1, placeholders_filtered, suggested_trade}. FILL CHECK: when the partition signal fires, arbitrage.fill_check prices it against live CLOB depth (theoretical_edge_pp_at_book vs realizable_edge_pp at 1000 shares/leg, thin_legs[]) — realizable_edge_pp ≤ 0 means the overround exists only at last-trade, not in the book; do not trade it. For custom sizing use polymarket_fill_risk.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventNoSingle-event mode (use this if you know the specific Polymarket event): event slug like "fed-decision-may-2026" or "when-will-bitcoin-hit-150k". Full Polymarket URLs also accepted.
topicNoCross-event mode (use this if you want to scan related events across the platform): a topic or seed question like "Fed rate decision" or "Strait of Hormuz traffic returns to normal". Tool searches Polymarket for related events and checks monotonicity across them.

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 already declare readOnlyHint, openWorldHint, idempotentHint. Description adds rich behavioral detail: logic of monotonicity violations, partition checks, Jaccard similarity filter, placeholder filter, fill check against CLOB depth. Explains response structure and 'do not trade' condition. No contradictions.

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?

Well-structured with logical sections (mode descriptions, semantic anchor, partition filter, fill check). Some redundancy (e.g., repeated mention of recommended mode). For a complex tool, the detail is warranted but could be slightly tighter.

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?

No output schema exists, so description fully covers return values: opportunities array with fields, partition_check details, fill check output. Explains edge cases (placeholder filtering, low similarity, realizable edge). Complete for a complex arbitrage detection tool.

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% with descriptions for both parameters. Description enriches understanding with examples ('fed-decision-may-2026'), accepted URL format, 'recommended' usage, and explanation of cross-event behavior. Goes well beyond schema detail.

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 ('Find arbitrage opportunities') and resource ('on Polymarket'), specifies the methods (monotonicity violations + partition-sum checks), and distinguishes three distinct modes (trending_scan, event, topic). It effectively differentiates from sibling tools like polymarket_edges or polymarket_fill_risk.

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?

Provides explicit usage guidance for each mode: 'Call with NO args for a trending_scan', 'event (recommended for a specific market)', 'topic for cross-event scanning'. Also advises when not to trade (realizable_edge_pp <= 0). Lacks direct comparison to alternatives but gives clear context for each mode.

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