Skip to main content
Glama

dnd5e

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?

While annotations already state readOnly, openWorld, idempotent, and destructiveHint=false, the description adds valuable behavioral context: thresholds (>3pp signal, ≥0.30 Jaccard similarity, >20% placeholder fraction), that it returns null signals in certain cases, and a fill check that warns against trading when realizable_edge_pp ≤ 0. 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 long but well-structured with clear sections (SEMANTIC ANCHOR, PARTITION FILTER, FILL CHECK) and front-loaded with the core purpose and modes. Every sentence adds necessary detail for a complex tool. It could be slightly more concise, but the length is justified by the tool's complexity.

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?

There is no output schema, so the description fully explains return values: 'opportunities[] (gap_pp, suggested_trade, reasoning, monotonicity violation context)' and 'partition_check{sum_yes_prices, gap_from_1, placeholders_filtered, suggested_trade}'. It also covers edge cases like placeholder filters and fill check realizability, making it complete for an agent.

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% and both event and topic parameters have descriptions, but the tool description adds significant meaning: it explains exactly what happens with each parameter (event walks child markets and checks ordering; topic flattens related events and runs comparator on union), includes example slugs, and describes output fields. This exceeds the baseline.

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 opens with a specific verb+resource+method: 'Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks.' It clearly distinguishes this from sibling tools like polymarket_edges (edge tracking) and polymarket_fill_risk (fill risk) by focusing on arbitrage via specific mathematical checks.

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?

It provides explicit usage modes: 'Call with NO args for a trending_scan', 'pass event for the strongest per-event partition_check', or 'topic for a themed cross-event scan.' It also gives an alternative for custom sizing: 'For custom sizing use polymarket_fill_risk.' This satisfies the 'when/when-not/alternatives' requirement.

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

All dnd5e 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

B3.4/5.0
Disambiguation2/5

Many tools have overlapping purposes, such as the three ask_pipeworx variants, the memory tools (remember/recall/forget), and the subscription management tools. Additionally, the D&D tools are mixed with a large set of unrelated tools, causing confusion between domains.

Naming Consistency2/5

Naming conventions are inconsistent: some tools follow verb_noun pattern (e.g., get_class, list_spells), while others use descriptive noun phrases (e.g., ai_visibility_check, polymarket_arbitrage). There is no clear, predictable pattern across the set.

Tool Count2/5

With 35 tools, the count is high for a server ostensibly focused on D&D 5e. The inclusion of many unrelated tools from the Pipeworx ecosystem makes the set feel bloated and unfocused for the intended domain.

Completeness1/5

For the D&D 5e domain, only 4 tools exist (get_class, get_monster, get_spell, list_spells), which is severely incomplete. The remaining tools cover other domains, but they do not serve the server's primary purpose, leaving obvious gaps in functionality.

Resources