Skip to main content
Glama

Excuse

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.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added
  2. Removed
  3. Added

TDQS

A5/5.0
Behavior5/5

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

The description adds substantial behavioral context beyond annotations: it walks the order-book ladder, returns a verdict (clean|degraded|cannot_fill), exposes per-leg fill details, and warns about 'forced_directional_risk' in basket mode. Annotations already declare readOnlyHint=true and destructiveHint=false, but the description enriches understanding of what the tool actually computes without contradicting annotations.

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?

The description is long but dense and well-structured. It front-loads the core purpose, then distinguishes modes with clear formatting, lists outputs, and concludes with actionable usage guidance. Every sentence adds value—no filler or 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?

Without an output schema, the description thoroughly enumerates return values for both modes (top_of_book, vwap_fill_price, slippage_pp, shares_filled, max_fillable_usd, verdict, theoretical_sum, capture_ratio, per-leg detail, thin_legs, etc.). It also explains the risk rationale, making it sufficient for an agent to decide whether this tool fits the task.

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?

Although schema coverage is 100% with descriptions for all four parameters, the tool description goes beyond by explaining mode semantics: how 'market' vs 'event' selects single vs basket mode, how 'side' defaults vary by mode, and how 'size_usd' is interpreted differently (spend/target proceeds vs settlement notional/shares per leg). This adds meaning not present in the schema alone.

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 itself from sibling tools by naming polymarket_arbitrage and polymarket_edges as the tools it precedes, positioning itself as a risk-check complement.

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?

Explicit usage guidance is given: 'USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500.' It also explains why (thin-book overround is not capturable) and the risk of partial fills, making when-to-use and when-not-to-use clear.

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

All Excuse 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.8/5.0
Disambiguation2/5

The ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, validate_claim) all route to the same underlying 5,708-tool catalog with subtle behavioral differences that are easy to misselect. Entity-focused tools (entity_profile, compare_entities, recent_changes, scan_competitor_ai_presence) also overlap heavily in the data they return, making boundaries fuzzy.

Naming Consistency3/5

All names use snake_case, but the word-order convention is mixed: verb-first (ask_pipeworx, compare_entities, discover_tools) coexists with noun-first (entity_profile, polymarket_arbitrage, recent_changes). The inconsistent reversal in excuse_generate versus generate_llms_txt further breaks the predictable pattern.

Tool Count2/5

At 32 tools the set is well past the well-scoped range, and several entries feel like padding: ask_pipeworx_beta duplicates ask_pipeworx, while the seven Polymarket tools and five company-intelligence tools could each be consolidated into fewer distinct capabilities. The broad scope justifies a large surface, but this count makes the server difficult to navigate.

Completeness3/5

The core data-lookup lifecycle (resolve, fetch, ground, validate, research, compare) is well covered, and memory/subscription features round it out. Obvious gaps include no direct tool to read a pipeworx:// citation URI (despite deep_research referencing one), and the excuse_generate tool is an isolated one-off with no supporting tools in its domain.

Resources