Skip to main content
Glama

Nuget

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

A4.9/5.0
Behavior5/5

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

Annotations indicate readOnly, openWorld, idempotent, non-destructive behavior. The description adds context: it checks live order-book depth and warns that thin books make theoretical overround uncapturable. No contradictions.

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 lengthy but well-structured with clear mode sections and bullet points for return fields. It is front-loaded with purpose and usage. Some verbosity could be trimmed, but the complexity of the tool 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?

No output schema exists, yet the description comprehensively lists all return fields for both modes, including risk indicators like thin_legs and forced_directional_risk. It also explains the dominant loss mode (partial basket fills). Highly complete.

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 coverage is 100%, but the description adds crucial context: explains the dual interpretation of size_usd (spend vs. target proceeds for singles; settlement notional for baskets) and the auto-side logic for basket mode. This goes beyond 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 clearly states the tool's core function: 'Realizable-vs-theoretical edge check against live CLOB order-book depth.' It distinguishes itself from sibling tools by specifying two modes (single-market and basket) and explicitly directs usage before acting on polymarket_arbitrage or polymarket_edges signals.

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: 'USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500.' It also explains when not to rely on theoretical values and warns about partial fill risks converting arb into directional positions.

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

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

B3.4/5.0
Disambiguation2/5

Several tools are near-identical: ask_pipeworx and ask_pipeworx_beta are explicitly the same function, ask_pipeworx_grounded is the same router with a different response mode, and polymarket_edges/polymarket_arbitrage/polymarket_edge_tracker/polymarket_fill_risk all overlap on prediction-market edge detection. search vs search_within vs discover_tools also blur discovery boundaries. An agent would struggle to pick the right tool without reading every long description.

Naming Consistency3/5

All names are snake_case and individually readable, so there's no chaotic style mixing. However, the pattern is inconsistent: bare verbs (search, recall, forget, subscribe), verb_noun (get_package, resolve_entity, scan_dependency), noun phrases (latest_version, recent_alerts), and compound prefixes (pipeworx_*, polymarket_*). The server is named 'Nuget' but the vast majority of tools carry pipeworx_ or polymarket_ prefixes, making the namespace feel like a grab-bag.

Tool Count2/5

35 tools is far too many for a server ostensibly named 'Nuget' — only ~5 tools relate to NuGet package lookup (search, get_package, list_versions, latest_version, scan_dependency), and even scan_dependency is npm-only. The remaining ~30 tools belong to an unrelated Pipeworx research/markets/memory platform. The count is inflated by redundant variants (ask_pipeworx trio, six polymarket tools) rather than distinct functionality.

Completeness2/5

Judged by the server's stated purpose (NuGet), the surface is thin and has dead ends: search and version metadata are covered, but there's no package owner/publisher info, no readme/description body fetch, no download stats beyond totals, and scan_dependency targets the wrong ecosystem (npm). Judged by the actual dominant domain (Pipeworx), coverage is excessive and sprawling. The tool set fails to deliver a coherent, complete surface for either apparent purpose.

Resources