Skip to main content
Glama

Realestateapi

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. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations indicate read-only, idempotent, open-world semantics. The description goes well beyond by detailing internal checks (semantic anchor, partition filter, fill check with CLOB depth), explaining return conditions (realizable_edge_pp ≤ 0 implies no valid trade), and describing output fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Though lengthy, every sentence is informative and adds value. The structure is logical: main purpose first, then mode explanations, followed by detailed sub-checks and response format. It earns its length without redundancy.

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?

The description fully compensates for the lack of output schema by explicitly listing response fields (opportunities[], partition_check, fill_check details). It covers all major behavioral aspects and handles edge cases (skipped_low_similarity, placeholders_filtered, thin_legs[]).

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 parameters with descriptions, but the tool description adds significant context: examples of event slugs, acceptance of full URLs, explanation of what topic does with seed questions, and the underlying logic (Jaccard similarity, placeholder filtering). This substantially aids correct parameter usage.

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 on Polymarket via monotonicity violations and partition-sum checks. It distinguishes between modes (no args, event, topic) and explains what each does, making the purpose unmistakable.

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 provides explicit guidance on when to use each call mode: no args for trending scan, event for a specific market (recommended), and topic for cross-event scanning. It even notes limitations such as partition filter and placeholder slugs, and suggests when to use polymarket_fill_risk for custom sizing.

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

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

Multiple tools have overlapping research/lookup purposes: ask_pipeworx and ask_pipeworx_beta are currently identical, ask_pipeworx_grounded and validate_claim both verify claims against sources, and six polymarket_* tools overlap on edge/arbitrage detection. The three realestateapi_* tools are distinct but sit awkwardly beside 31 unrelated tools.

Naming Consistency2/5

Naming conventions are mixed: snake_case prefixed tools (realestateapi_property_search), domain-prefixed tools (polymarket_edges), verb-noun tools (ask_pipeworx, compare_entities), noun phrases (entity_profile, recent_changes), and bare verbs (remember, forget, recall). There is no consistent verb_noun pattern across the set.

Tool Count2/5

34 tools is heavy, and the vast majority belong to the Pipeworx platform rather than the Realestateapi identity — only 3 of 34 tools are real-estate specific. The count is not well-scoped for the server's stated purpose.

Completeness2/5

For a real estate API the surface is severely thin: search, detail, and skip-trace only, with no market trends, tax history, rental estimates, or comparable-sales data. For the Pipeworx meta-domain the coverage is broader, but the server presents as Realestateapi, making the domain coverage a mismatch.

Resources