Skip to main content
Glama

Macvendors

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.8/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds significant value by explaining the output structure, the ladder-walking process, and critical risks like unhedged directional positions from partial fills, which goes beyond annotation information.

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, a front-loaded summary, and every sentence adds value. It could be slightly more concise in the basket description, but overall it is efficiently organized.

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 thoroughly explains all return fields for both modes, including edge cases like thin legs and forced directional risk. It covers the complex dual-mode behavior and warns about the dominant loss mode, making it complete for such a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds context such as auto-detection of side for basket mode, interpretation of size_usd as settlement notional for baskets, and clamping bounds. This provides meaningful additional semantics 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 clearly states 'Realizable-vs-theoretical edge check against live CLOB order-book depth' with specific verbs and resource distinction between single-market and basket modes. It explicitly differentiates from siblings like polymarket_arbitrage and polymarket_edges by indicating when to use this tool.

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 directives: 'USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500'. It explains the risks of partial basket fills and the consequences of not using this tool, giving clear guidance on when and why to use it.

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

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

Several tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded share the same router, with the beta variant currently identical to stable. The five polymarket_* tools plus bet_research also blur boundaries, and discover_tools/suggest_questions both serve discovery. Detailed descriptions help, but an agent could easily select the wrong tool.

Naming Consistency3/5

All names use lower_snake_case and many follow a clear verb_noun pattern (resolve_entity, validate_claim, generate_llms_txt). However, there are notable deviations: entity_profile, pipeworx_feedback, polymarket_edges, recent_changes, and bet_research lead with nouns or adjectives. The style is readable and predictable in clusters, but not uniform.

Tool Count2/5

32 tools is well above the 25+ threshold for 'too many', and the server name Macvendors suggests a narrow MAC-lookup service, yet most tools belong to a much broader Pipeworx data/prediction-market platform. Several tools are near-duplicates or micro-variants (three ask_pipeworx versions, six polymarket tools). The set would be more appropriately split or heavily consolidated.

Completeness4/5

Within the actual broad research platform domain, the surface is fairly complete: discovery, routing, grounded answers, entity profiles, comparisons, recent changes, claim validation, semantic search, prediction-market analysis, subscriptions, memory, and feedback are all covered. Minor gaps exist, such as no subscription update tool and no batch MAC lookup, but agents can generally complete workflows without dead ends.

Resources