Skip to main content
Glama

Discogs

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. Changed1 schema field changed
    • removedInput schema / anyOf
      Removed value: -[
-  {
-    "required": [
-      "event"
-    ]
-  },
-  {
-    "required": [
-      "topic"
-    ]
-  }
-]
  2. Changed3 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "event"
+    ]
+  },
+  {
+    "required": [
+      "topic"
+    ]
+  }
+]
    • changedInput schema / properties / event / description
      Previous value: -"Single-event mode: Polymarket event slug (e.g. \"when-will-bitcoin-hit-150k\") or full URL."New value: +"Single-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."
    • changedInput schema / properties / topic / description
      Previous value: -"Cross-event mode: a topic or seed question. Tool searches Polymarket for related markets across separate events and checks monotonicity across them. E.g. \"Strait of Hormuz traffic returns to normal\"."New value: +"Cross-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."
  3. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already indicate read-only, open-world, idempotent, non-destructive behavior. Description adds detailed behavioral context: semantic anchor (Jaccard similarity), partition filter (placeholder slugs), fill check (realizable vs theoretical edge), and response structure. 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?

Description is thorough but verbose (multiple paragraphs). However, it is well-structured with clear sections for each mode and additional details. Every sentence adds value; minor redundancy could be trimmed but overall effective.

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?

Despite no output schema, description explains the response structure (opportunities array, partition_check, fill check) and all edge cases (placeholder filtering, similarity threshold, fill risk). Covers all modes thoroughly. Very complete for a complex 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%, but description greatly expands on each parameter: 'event' expects a slug or URL, 'topic' expects a seed question for cross-event scanning. Explains how they work (walks child markets, checks monotonicity, partition check) and their output differences.

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 explicitly states the tool finds arbitrage opportunities via monotonicity violations and partition-sum checks, and distinguishes three modes (trending scan, event, topic). This is specific, uses strong verbs, and differentiates from siblings which are unrelated or focus on edges/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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear guidance on when to use each mode: no args for trending scan, 'event' for a specific market (recommended), 'topic' for cross-event scanning. Explains trade-offs like cross-event catching patterns single-event misses, and includes fill check to avoid non-tradeable signals.

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

All Discogs 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
Disambiguation1/5

There is severe overlap among tools: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical variants, and deep_research, discover_tools, and suggest_questions all serve discovery/research purposes. The Discogs-specific tools are distinct, but the large number of redundant Pipeworx tools makes it impossible to tell which one to pick.

Naming Consistency2/5

The Discogs tools follow a clean verb_noun pattern (get_artist, get_label, get_master, get_release), but the majority of the set uses inconsistent, domain-specific names (deep_research, generate_llms_txt, polymarket_arbitrage, scan_competitor_ai_presence). No single naming convention is applied across the server.

Tool Count1/5

With 36 tools, the server is massively over-provisioned for a Discogs-focused API. Most tools (e.g., ask_pipeworx, polymarket_edges, SEC lookups) have nothing to do with Discogs and belong to a separate service. The Discogs surface alone could be served by ~6 tools (search, get_artist, get_label, get_master, get_release, search_within), so the count is wildly inappropriate.

Completeness3/5

For the Discogs domain, the core entities (artist, label, master, release) and full-text search are present, plus semantic search inside records. However, there are gaps like user collections, wantlists, marketplace, and discogs-specific filters beyond format/country. The presence of many unrelated tools does not directly hurt domain coverage, but the Discogs surface is not exhaustive.

Resources