Skip to main content
Glama

Geoboundaries

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

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

Annotations declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. The description adds substantial behavioral context beyond these: mode requirements, default sides, size interpretation differences (spend vs target proceeds vs settlement notional), return fields including verdicts, and critical risk disclosure about partial basket fills. It does not contradict 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 long but information-dense, with every sentence adding necessary detail. It is structured by mode (SINGLE-MARKET vs BASKET) and uses clear delimiters (e.g., 'REQUIRES', 'USE THIS'). However, it is a single dense paragraph that could benefit from bullet points or section breaks to improve scanability, though no content is redundant.

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 covers return values for both modes: top_of_book, vwap_fill_price, slippage_pp, verdict, theoretical_sum vs realizable_sum, capture_ratio, profit_usd, per-leg fill detail, thin_legs[], and max_clean_notional_usd. It also covers edge cases (cannot_fill verdict, forced_directional_risk) and provides the 'why' behind usage, making it 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 description coverage is 100%, so baseline is 3, but the description enriches every parameter significantly. It explains the market/event mode distinction, the auto-detection logic for basket side, and the nuanced meaning of size_usd per mode (spend vs target proceeds vs settlement notional, with clamp range). This far exceeds the schema's terse parameter 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 opens with a specific, meaningful purpose: 'Realizable-vs-theoretical edge check against live CLOB order-book depth.' It clearly distinguishes this tool from siblings by naming the arb-check use case and referencing polymarket_arbitrage and polymarket_edges explicitly. The verb 'check' plus resource 'live CLOB order-book depth' is specific and actionable.

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 usage guidance is provided: 'USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500.' It also explains the two modes (single-market vs basket), when each is appropriate, and the rationale (theoretical overround on thin books is not capturable, partial basket fills lead to unhedged directional risk). This goes beyond generic context and names concrete alternatives.

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

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

Many tools have overlapping or unclear purposes, e.g., multiple entity research tools (entity_profile, recent_changes, compare_entities, validate_claim) and several betting tools (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_kalshi_spread). The memory tools (remember, recall, forget) and generic lookup tools (ask_pipeworx, discover_tools) further blur boundaries, making it hard for an agent to consistently select the right tool.

Naming Consistency2/5

Tool names follow no consistent pattern: some use snake_case verbs (forget, recall, remember), others are noun phrases (entity_profile, recent_changes), and many have mixed conventions (ai_visibility_check, ask_pipeworx, bet_research). There is no clear verb_noun structure, and the naming style varies widely across the set.

Tool Count3/5

At 22 tools, the count is within a reasonable range, but the server's stated purpose ('Geoboundaries') is severely mismatched with the actual tool set, which covers data retrieval, betting, memory, and more. The number is not excessive for the breadth of functionality, but it feels bloated for a server that should be focused on geographic boundaries.

Completeness1/5

The server is named 'Geoboundaries' but only provides two boundary-related tools (get_boundaries, get_geometry). The remaining 20 tools are unrelated, covering general data access, betting arbitrage, and memory operations. This leaves massive gaps for the implied domain (no tools for boundary editing, search by location, or other geographic operations) while over-supplying tools for unrelated tasks.

Resources