Skip to main content
Glama

Nws

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 indicate read-only, open-world, idempotent, non-destructive. The description adds significant behavioral context: details on monotonicity checks, partition sum checks, semantic anchor (Jaccard similarity), partition filter (placeholder slugs), fill check against live CLOB depth, 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?

The description is well-structured with a clear breakdown of modes, but it is somewhat long and includes some redundancy (e.g., cross-event mode explanation in two places). Every sentence adds value, but it could be slightly more concise without losing information.

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 complexity (multiple modes, algorithmic details, response fields), the description is thorough. It covers all aspects: purpose, usage, behavior, parameters, output structure (enumerated), and even trading guidance. No output schema but the description compensates adequately.

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 describes both optional parameters with 100% coverage. The description adds meaning: explains acceptable formats (slugs, URLs), distinguishes event vs topic modes, and describes the behavior triggered by each parameter. This goes beyond the schema's field descriptions.

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 tool finds arbitrage opportunities on Polymarket via monotonicity violations and partition-sum checks. It distinguishes three modes: no-args trending scan, event mode for specific slugs, and topic mode for cross-event scanning. This differentiates it 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 Guidelines5/5

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

The description explicitly tells when to use each mode: no args for trending, event for a specific market, topic for cross-event scanning. It provides examples of valid inputs (slugs, URLs, seed questions) and explains the cross-event mode catches patterns missed by single-event. It also advises when not to trade (if realizable_edge_pp ≤ 0).

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

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

Many tools have overlapping purposes, e.g., multiple Polymarket analysis tools, several query tools (ask_pipeworx, deep_research, compare_entities, entity_profile) with unclear boundaries. Agents may struggle to choose the correct tool.

Naming Consistency3/5

While most names use snake_case, there is no consistent prefix pattern across subdomains (e.g., 'ask_', 'get_', 'polymarket_', 'pipeworx_'). Some names like 'bet_research' and 'deep_research' follow different conventions within the same domain.

Tool Count2/5

34 tools is excessive for a server named 'Nws' that primarily suggests weather. The set covers many unrelated domains (prediction markets, npm scanning, memory), making the scope unfocused and overloaded.

Completeness3/5

The server has decent coverage for prediction markets and company financials, but weather tools are limited to basic forecasts/alerts, lacking radar, climate, or historical data. Other domains like npm scanning seem tacked on.

Resources