Skip to main content
Glama

Osf

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

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

Annotations already indicate readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds details about live order-book checking, verdict types (clean/degraded/cannot_fill), and forced directional risk. It warns of the dominant loss mode from partial basket fills, which goes beyond 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 sections for each mode and ends with usage rationale. While somewhat verbose, every sentence is informative and front-loaded. Could be slightly tighter, but effectively balances detail and structure.

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 return values for both modes (e.g., top_of_book, vwap_fill_price, verdict for single-market; capture_ratio, profit_usd, thin_legs for basket). It covers when to use, output details, and risk factors, making it fully 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 significant context: mode-dependent interpretations of size_usd (spend vs target proceeds vs settlement notional), default side behavior in basket mode (auto from partition sum), and the REQUIRES constraint for market or event. This enriches the schema descriptions.

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 defines the tool as a 'realizable-vs-theoretical edge check against live CLOB order-book depth'. It distinctly separates single-market and basket modes, and provides specific metrics returned (verdict, fill details). This distinguishes it from siblings like polymarket_arbitrage by focusing on fill risk.

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 guidance: 'USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500'. It explains the rationale (theoretical overround not capturable, partial fills create directional risk) and differentiates modes. No explicit 'when not to use', but the positive guidance is comprehensive.

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

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

Several tools have near-identical or heavily overlapping purposes: ask_pipeworx and ask_pipeworx_beta are currently identical, ask_pipeworx and validate_claim both answer factual questions, and discover_tools and suggest_questions both surface capabilities. The dense set of Polymarket and entity-research tools further blurs boundaries despite long descriptions.

Naming Consistency3/5

Names are consistently snake_case, but they do not follow a single predictable verb_noun pattern: actionable names like ask_pipeworx, search_projects, and compare_entities mix with noun-style names like polymarket_edges, pipeworx_feedback, and recent_changes. The convention is readable but not uniform.

Tool Count2/5

34 tools exceeds the reasonable scope for a coherent server, and many are near-duplicate variants or members of sprawling tool families (ask_pipeworx variants, multiple Polymarket scanners, several meta/discovery tools). The set would be stronger with consolidation around a smaller number of distinct capabilities.

Completeness1/5

If this server is meant to provide OSF access, the surface is severely incomplete: only search_projects, search_preprints, and get_project exist, with no create/update/delete, file handling, registration, or contributor access. If it is meant to be a broader Pipeworx assistant, the OSF tools are unrelated and the domain is so scattered that coverage is incoherent.

Resources