Skip to main content
Glama

Geonames

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

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint (all safe). The description adds rich behavioral context: walks the order book ladder, returns verdicts (clean|degraded|cannot_fill), warns about thin books and forced directional risk. This goes beyond annotations to explain exactly what the tool does internally and what risks it mitigates.

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 relatively long but well-structured: starts with purpose, then uses clear section headers for SINGLE-MARKET and BASKET modes. Every sentence adds value (no filler). However, it could be slightly more concise without losing clarity, hence a 4 instead of 5.

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 lacking an output schema, the description fully documents all return values for both modes (top_of_book, verdict for single-market; theoretical_sum, capture_ratio, thin_legs for basket). It explains edge cases (thin books, partial fills) and the dominant loss mode. Combined with high schema coverage and annotations, the description is complete for the tool's complexity.

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%, and the description adds significant meaning beyond schema field descriptions. For example, it explains that `size_usd` for basket is 'settlement notional — shares per leg, each paying $1 at resolution,' and describes default behavior for `side` in basket mode (auto-detect based on partition sum). Each parameter's role in both modes is clearly elaborated.

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?

Description clearly states it performs a 'realizable-vs-theoretical edge check against live CLOB order-book depth.' It distinguishes single-market and basket modes with precise verb-resource combinations. Additionally, it explicitly ties usage to sibling tools by stating 'USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500,' making its purpose unambiguous and distinct.

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 when-to-use guidance: before acting on arbitrage signals or edge trades above ~$500. It also explains when-not-to-use by warning about partial basket fills converting arb into unhedged directional positions. Requirements are clear (one of `market` or `event`), and the two modes are thoroughly explained with usage context.

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

All Geonames 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, ask_pipeworx_grounded; multiple polymarket_* scanners), and the mix of unrelated domains makes it hard to tell which tool is canonical for a task. The few geographic tools are distinct, but they are buried among dozens of non-geographic tools.

Naming Consistency2/5

Naming is a mix of verb_noun (search_geonames, resolve_entity), proper-noun prefixes (pipeworx_*, polymarket_*), and descriptive phrases (ask_pipeworx, bet_research, scan_competitor_ai_presence). No consistent pattern or verb style across the set.

Tool Count2/5

35 tools is far more than a Geonames-focused server needs, and most are unrelated to geospatial data. The count would be borderline for a general data platform, but it is excessive and unfocused for the stated server name.

Completeness1/5

The geographic surface is severely incomplete: only four tools (search_geonames, get_nearby, find_postal_codes, get_timezone) cover a tiny sliver of typical Geonames functionality like reverse geocoding, elevation, or distance calculations. The many non-geographic tools do not compensate for the missing core domain coverage.

Resources