Skip to main content
Glama

Virustotal

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.8/5.0
Behavior5/5

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

Discloses internal processes: walks child markets, computes partition_sum checks, applies Jaccard similarity threshold (≥0.30), filters placeholder slugs, and performs fill check against CLOB depth. No contradiction with annotations (readOnlyHint, idempotentHint, destructiveHint).

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 slightly verbose. Uses semantic capitalization for key concepts and clear separation of modes. Could be more terse, but every sentence adds value.

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 details response structure (opportunities array, partition_check object with field names). Covers edge cases (low Jaccard similarity, placeholder filtering, fill check details). Fully explains behavior for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds significant context: event accepts full URLs, topic triggers cross-event search with similarity filtering. Explains behavior differences beyond schema definitions.

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?

States verb 'Find arbitrage opportunities' with specific methods (monotonicity violations + partition-sum checks). Distinguishes modes (no args, event, topic) and differentiates from sibling tools like polymarket_fill_risk and polymarket_edges.

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?

Explicitly instructs when to use each mode: no args for trending scan, event for a specific market slug, topic for cross-event scanning. Provides rationale for cross-event mode and warns against trading when fill check shows non-realizable edge.

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

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

The set mixes several overlapping families: ask_pipeworx and ask_pipeworx_beta are described as currently identical, while ask_pipeworx_grounded, deep_research, bet_research, and validate_claim all route to the same underlying data sources. Polymarket tools (arbitrage, edges, edge_tracker, fill_risk, spread) also blur together; only the four lookup_* VirusTotal functions are cleanly distinct.

Naming Consistency3/5

Names are uniformly snake_case with a few consistent families (lookup_domain/file/ip/url, ask_pipeworx_*, polymarket_*), which helps. However, the set mixes imperative verbs (remember, forget, subscribe, validate_claim), noun phrases (entity_profile, deep_research, recent_alerts), and inconsistent prefixes, so no single naming convention holds across the server.

Tool Count2/5

35 tools is too many for the apparent purpose, especially for a server named Virustotal. The bulk of the tools address unrelated Pipeworx research, memory, and prediction-market functions, so the count does not reflect the server's advertised domain.

Completeness1/5

For a VirusTotal server, only four lookup tools exist and there is no way to submit a URL/file, create a scan, retrieve analysis details, or explore relationships—core VirusTotal operations are missing. Scoped broadly, the unrelated Pipeworx tools are extensive, but they do not fill the gaps in the advertised domain. The surface is severely incomplete relative to the server name.

Resources