Skip to main content
Glama

spacenews

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.

TDQS

A4.9/5.0
Behavior5/5

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

Despite readOnlyHint and idempotentHint, the description adds substantial behavioral detail: partition_check threshold of >3pp, Jaccard similarity ≥0.30 for semantic anchoring, placeholder slug filtering (>20% returns null), and fill-check behavior with realizable_edge_pp ≤ 0 warning not to trade. It also explains skipped_low_similarity count and response shape.

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 dense and long, but each section (SEMANTIC ANCHOR, PARTITION FILTER, FILL CHECK) adds unique operational detail. It is front-loaded with mode selection and ends with alternatives, but uses ALL-CAPS labels and includes internal function references (arbitrage.fill_check) that add length; still, it earns its place for a complex tool.

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?

For a tool with two optional parameters, no output schema, and complex multi-mode behavior, the description thoroughly covers response fields, edge cases, and anti-trading warnings. It even explains the difference between theoretical and realizable edge, making it self-sufficient.

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?

Input schema covers both params with brief descriptions, but the tool description enriches them with concrete examples (event slugs like 'fed-decision-may-2026', topic seeds), notes that full URLs are accepted for event, and clarifies that no args triggers trending_scan. This goes well beyond the schema.

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: 'Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks.' It clearly distinguishes from siblings by naming the detection methods and explaining three invocation modes (no args, event, topic).

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 explicitly tells when to call with no args (trending_scan), when to use event mode (specific market), and when to use topic mode (cross-event themed scan), even recommending event for a specific market. It also directs users to sibling tool polymarket_fill_risk for custom sizing, providing an explicit alternative.

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

All spacenews 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
Disambiguation3/5

Several tools have overlapping purposes, such as ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research. While each has distinct nuances, they could be confused by an agent.

Naming Consistency3/5

Most tools use snake_case, but the naming pattern is inconsistent (e.g., bet_research vs. polymarket_arbitrage vs. ai_visibility_check). There is no strong verb_noun pattern across the set.

Tool Count2/5

34 tools is high given the server's stated purpose ('spacenews'). Only a few tools directly relate to space news; the bulk are general-purpose Pipeworx utilities, making the scope too broad.

Completeness2/5

For a space news server, the tool surface is incomplete: only get_articles, get_blogs, and search_articles are relevant. Missing tools for article details, source filtering, or categories. The extensive general tools don't make up for this gap.

Resources