Skip to main content
Glama

Crates

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?

Annotations already declare readOnlyHint, openWorldHint, idempotentHint true, and destructiveHint false. The description adds rich behavioral context: it walks the order book ladder, returns fill details and verdicts (clean/degraded/cannot_fill), and warns about forced directional risk in basket mode. No contradiction with annotations.

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 well-structured with clear sections for single-market and basket modes, and front-loads the purpose. Every sentence provides essential guidance given the tool's complexity. Slight verbosity in explaining return fields, but justifiable.

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?

No output schema exists, so the description fully explains return values for both modes (e.g., top_of_book, vwap_fill_price, capture_ratio, thin_legs). It covers all aspects: modes, parameters, return fields, and warnings. Annotations complement well.

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?

Schema description coverage is 100% with each parameter described. The description adds further semantics: default values for side, size_usd interpretation differences between single-market and basket, and how auto side works in basket mode. This adds value 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 starts with a clear verb+resource: 'Realizable-vs-theoretical edge check against live CLOB order-book depth.' It distinguishes single-market from basket modes, and its purpose (assessing fill risk) is clearly distinct from sibling tools like polymarket_arbitrage 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?

The description explicitly states 'USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500.' It explains when to use (theoretical overround may not be capturable) and warns about partial basket fills converting arb into directional positions. It also specifies required parameters for each mode.

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

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

A4/5.0
Disambiguation3/5

The tool set includes several overlapping research/lookup tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, entity_profile) and multiple Polymarket tools, which could confuse an agent despite detailed descriptions. The boundaries between these tools are explained in the descriptions, but the sheer number of similar-purpose tools creates ambiguity.

Naming Consistency4/5

Most tools follow a verb_noun pattern (e.g., search_crates, get_versions, validate_claim), but there are exceptions like entity_profile, deep_research, and bet_research, which break the pattern. The overall naming is readable and mostly consistent, with the polymarket_ and pipeworx_ prefixes providing grouping.

Tool Count2/5

With 35 tools, the server is far too heavy for a focused service. The server name 'Crates' suggests a narrow domain, but only 5 tools relate to Rust crates, while the rest cover disparate areas (Pipeworx, Polymarket, memory management). This mismatch and high count make the tool surface unwieldy.

Completeness4/5

For the underlying Pipeworx/Polymarket domain that the majority of tools serve, the coverage is strong: lookup, grounded answers, research, entity profiles, comparisons, changes, claim validation, scanning, memory, subscriptions, tool discovery. Minor gaps exist (e.g., no direct summarization), but the set feels well-rounded for a data analysis agent.

Resources