Skip to main content
Glama

Openrouter

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?

The description adds significant behavioral context beyond annotations: it walks the order book ladder, returns specific fields (top_of_book, slippage, etc.), and warns about the dominant loss mode. Annotations already indicate read-only, idempotent, non-destructive, so no contradiction.

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-structured with headings and bullet points, front-loading the purpose. It is thorough but not overly verbose; every sentence adds value. Minor room for tightening, but otherwise efficient.

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?

Despite no output schema, the description lists all return fields in parentheses. It covers two modes, parameter nuances, and risk warnings. Given the tool's complexity, this description is comprehensive and leaves no critical gaps.

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%, but the description enhances meaning: it explains side default behavior (auto in basket), size_usd interpretation (spend vs target proceeds), and mode-specific implications. This goes beyond the schema's basic 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 states it performs a 'Realizable-vs-theoretical edge check against live CLOB order-book depth' and distinguishes two modes (single-market vs basket). It provides specific verb and resource, differentiating it 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?

Explicitly tells the agent when to use this tool: 'USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500'. It also explains why (partial basket fills convert arb into unhedged position), providing clear context and alternatives.

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

All Openrouter 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.9/5.0
Disambiguation3/5

Several tools overlap in purpose: ask_pipeworx and ask_pipeworx_beta are explicitly identical today, and the polymarket_edges, polymarket_arbitrage, bet_research, and polymarket_fill_risk tools all orbit market-opportunity analysis from slightly different angles. The descriptions are unusually detailed and often say when to prefer one tool over another, but an agent must read carefully to avoid misselection.

Naming Consistency4/5

Names are consistently snake_case and mostly follow a verb_noun pattern (list_models, get_model, resolve_entity, validate_claim, scan_dependency), with predictable domain prefixes like polymarket_* and pipeworx_*. A few noun-first names like entity_profile, bet_research, and ai_visibility_check deviate slightly, but the overall convention is readable and coherent.

Tool Count2/5

34 tools is well into the 'too many' range, especially for a server named Openrouter that actually spans several unrelated domains: model catalog, Pipeworx data retrieval, Polymarket analysis, memory, subscriptions, and website tooling. Many individual tools are justified, but the set is overstuffed and would be better split into focused servers.

Completeness3/5

Each sub-domain is reasonably covered: model catalog has list/get/compare, memory has remember/recall/forget, subscriptions have subscribe/list/unsubscribe/recent_alerts, and Pipeworx querying has multiple modes plus discovery. However, a server named Openrouter exposes no way to actually run completions or route requests through OpenRouter, and the unrelated bundled domains make the overall surface feel scattered rather than complete.

Resources