Skip to main content
Glama

wikipedia

by io.github.pipeworx-io

Polymarket Fill Risk

polymarket_fill_risk
Read-onlyIdempotent

Realizable-vs-theoretical edge check against live CLOB order-book depth. REQUIRES one of market (single-market mode) or event (basket/partition mode). SINGLE-MARKET: pass a market slug/URL + side (buy_yes|sell_yes|buy_no|sell_no, default buy_yes) + size_usd (default 1000 — max spend on buys, target proceeds on sells); walks the ladder and returns top_of_book, vwap_fill_price, slippage_pp, shares_filled, max_fillable_usd, and a verdict (clean|degraded|cannot_fill). BASKET: pass an event slug/URL + side (sell_yes = capture overround by selling every leg, buy_yes = capture underround; default auto from partition sum) + size_usd interpreted as settlement notional S (shares per leg; each share pays $1); returns theoretical_sum vs realizable_sum (top-of-book vs VWAP across all legs), capture_ratio, profit_usd at executed size, per-leg fill detail, thin_legs[], max_clean_notional_usd, and forced_directional_risk naming the legs most likely to strand you unhedged. USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500 — theoretical overround on thin books is not capturable, and partial basket fills convert an arb into an unhedged directional position (the dominant loss mode in real arb-bot P&L).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sideNoSingle-market: buy_yes | sell_yes | buy_no | sell_no (default buy_yes). Basket: sell_yes | buy_yes (default auto — sell if partition sum > 1, buy if < 1).
eventNoBasket mode: event slug or full polymarket.com URL — checks every leg of the partition.
marketNoSingle-market mode: market slug or full polymarket.com URL.
size_usdNoSingle-market: USD to spend (buys) or target proceeds (sells). Basket: settlement notional — shares per leg, each paying $1 at resolution. Default 1000, clamp 10–1,000,000.

TDQS

A4.9/5.0
Behavior5/5

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

The description discloses behavior far beyond the annotations: it walks the order-book ladder, returns specific metrics (top_of_book, vwap_fill_price, slippage_pp, etc.), and warns that partial basket fills convert an arb into an unhedged directional position—critical risk context. No contradiction with readOnlyHint/openWorldHint/idempotentHint.

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 extremely dense; every sentence carries actionable detail. It is front-loaded with the core purpose and then structured by mode. Slightly verbose, but the complexity of two modes and risk guidance justifies the length.

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 no output schema, the description enumerates return values for both modes (top_of_book, vwap_fill_price, capture_ratio, thin_legs[], etc.), covers all four parameters with mode-specific meaning, and includes practical risk warnings. It is fully self-contained for a complex tool.

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?

Though the schema has 100% coverage, the description adds substantial semantics: explains how size_usd is interpreted differently in single-market (max spend/target proceeds) vs basket (settlement notional, shares per leg), defines the default side logic in basket mode, and mentions clamping. This is meaningful addition over 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: 'Realizable-vs-theoretical edge check against live CLOB order-book depth.' It clearly distinguishes this from sibling tools like polymarket_arbitrage and polymarket_edges by focusing on fill risk rather than signal detection or theoretical edge.

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 states when to use: 'USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500.' It also contrasts single-market vs basket modes, giving clear context for choosing between them.

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

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

Several tool families have ambiguous boundaries: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are three variants of the same router (with beta currently identical), and the six polymarket tools plus bet_research heavily overlap in scanning and pricing edges. discover_tools, suggest_questions, and deep_research also all function as 'what should I query' entry points. Agents will struggle to select the right tool without carefully reading long descriptions.

Naming Consistency3/5

Many tools follow a clear verb-first snake_case pattern (get_article_extract, resolve_entity, subscribe, validate_claim), and families like ask_pipeworx_* and polymarket_* are internally consistent. However, notable noun-phrase outliers such as entity_profile, deep_research, bet_research, recent_changes, pipeworx_feedback, and polymarket_edge_tracker break the convention. The naming is readable but not predictable across the full set.

Tool Count2/5

36 tools is well over the 25+ threshold for a typical MCP server, and for a server named 'wikipedia' it is especially disproportionate: only 5 tools actually deal with Wikipedia while 31 are Pipeworx data, prediction-market, memory, subscription, and feedback utilities. The count reflects a broad all-in-one platform crammed into a Wikipedia-labeled surface rather than a well-scoped server. This is a significant scope mismatch.

Completeness4/5

The Wikipedia portion is reasonably complete for read-only lookup: search, summary, sections, full extract, and random discovery cover common encyclopedic questions without dead ends. The broader Pipeworx surface is also extensive, with query, grounded verification, deep research, entity resolution/profile/comparison, claim validation, memory, and subscription lifecycle tools. Minor gaps remain (no article categories/history, no update for subscriptions, no direct fetch of a citation URI), but they are workable.

Resources