Skip to main content
Glama

Sgd

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

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

Annotations already declare read-only and idempotent, but the description adds valuable behavioral details: walking the ladder, returning verdicts like clean/degraded/cannot_fill, and identifying forced directional risk. No contradictions 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 well-organized with clear mode sections and emphasis, but it is somewhat verbose. Every sentence adds value, but could be tightened slightly without losing clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, but the description enumerates all key return fields for both modes, covering top_of_book, VWAP, slippage, and risk metrics. Lacks explicit error handling details, but overall complete 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?

Schema coverage is 100%, but the description adds significant meaning: explains the dual meaning of size_usd (spend vs target proceeds in single-market, settlement notional in basket), clarifies default side logic for baskets, and specifies clamp ranges beyond the schema's brief comments.

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 it performs a realizable-vs-theoretical edge check using live order-book depth, distinguishing between single-market and basket modes. It differentiates from siblings like polymarket_arbitrage by focusing on capturability of theoretical 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?

Explicitly instructs to use this tool before acting on polymarket_arbitrage signals or polymarket_edges trades above ~$500, and explains the risks of partial fills and uncapturable overround. Provides clear when-to-use guidance and rationale.

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

All Sgd 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.6/5.0
Disambiguation2/5

Several tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta (explicitly identical today), ask_pipeworx_grounded, deep_research, and validate_claim all route factual questions through similar pipelines. The polymarket_* cluster also blurs together, with arbitrage, edges, fill_risk, kalshi_spread, and bet_research all analyzing prediction-market mispricings from different angles.

Naming Consistency3/5

All names use consistent snake_case, but the verb/noun pattern is mixed: some are verb-first (compare_entities, generate_llms_txt, validate_claim), others noun-first (polymarket_edges, entity_profile, ai_visibility_check), and some are bare product names (ask_pipeworx, pipeworx_trending). Readable overall, but no single predictable convention.

Tool Count2/5

34 tools is far too many for a coherent server, especially since the server is named 'Sgd' but only 3 tools relate to yeast genetics. The remaining 31 tools span data lookup, prediction markets, memory, subscriptions, npm scanning, and llms.txt generation—an unfocused grab bag that should be split into multiple servers.

Completeness2/5

As an SGD yeast-genome server, the surface is thin: search, get_gene, and get_gene_go cover basic lookup but miss sequences, interactions, strains, homologs, and other standard SGD data. As a general data utility, the collection is broad but incoherent, with several one-off tools (generate_llms_txt, scan_dependency) that have no connection to the rest.

Resources