Skip to main content
Glama

Google_maps

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

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

Annotations declare readOnly, openWorld, idempotent, non-destructive. The description adds behavioral details like live order-book checking, required parameters (market or event), default and clamp behavior, and return fields including a verdict. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but every sentence is necessary for the tool's complexity (two modes, multiple return fields, usage warnings). It is front-loaded with the core purpose and structured logically. No waste.

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?

For a tool with 4 parameters, no output schema, and complex dual-mode behavior, the description is remarkably complete. It enumerates return fields, explains risk of partial fills, and covers default and clamp behavior. Adequate for agent invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all 4 parameters. The description adds context on parameter interaction (exclusivity of market/event, side default for basket, size_usd dual meaning) but does not significantly extend beyond schema. Baseline 3 is appropriate.

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 the tool "check realizable-vs-theoretical edge against live CLOB order-book depth", specifying verb and resource. It distinguishes two modes (single-market and basket) and lists return values, differentiating it from sibling polymarket tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly advises use before acting on polymarket_arbitrage signals or trades above $500. It also warns against partial basket fills leading to directional risk. While clear on when to use, it lacks explicit when-not-to-use guidance for small trades or other scenarios.

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

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

The tool set mixes unrelated domains (maps, prediction markets, npm dependencies, memory storage) under one server named 'Google_maps'. While individual tool descriptions are clear, an agent cannot easily distinguish which tools belong to the maps domain and which are extraneous, causing confusion about the server's actual purpose.

Naming Consistency2/5

Tool names lack a consistent convention. Maps tools use 'maps_' prefix, but other tools have names like 'ask_pipeworx', 'bet_research', 'forget', etc., mixing prefixes, verb styles, and underscore usage. No unified naming pattern across the set.

Tool Count2/5

37 tools is excessive for a specialized maps server. Only 7 tools are map-related; the remaining 30 cover disparate domains (financial data, prediction markets, system utilities), making the server seem like a random collection rather than a focused integration.

Completeness2/5

For a maps server, common operations like static map generation, place photos, or timezone lookups are missing. The inclusion of many non-maps tools creates a 'kitchen sink' effect, undermining completeness for the stated purpose. The tool surface is severely incomplete if judged by the server name.

Resources