Skip to main content
Glama

Guidetopharmacology

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

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

Description adds significant behavioral context beyond annotations (readOnlyHint, idempotentHint, etc.): it walks the ladder, returns verdicts (clean/degraded/cannot_fill), and for basket mode details per-leg fills, thin_legs, and forced_directional_risk. Annotations already indicate non-destructive, read-only behavior; description confirms and enriches without 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 long but well-organized: it starts with the core purpose, then clearly separates single-market and basket modes with headings, lists return fields, and ends with usage guidance. Every sentence adds value; nothing is redundant. While dense, it earns its length given the tool's complexity.

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 the tool's two modes, four parameters, no output schema, and complex behavior (ladder walking, per-leg details), the description is remarkably complete. It covers all inputs, explains all significant return fields, and warns about critical failure modes (partial fills, directional risk). No important aspect is left unexplained.

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?

All four parameters have descriptions in the schema (100% coverage), but the description adds essential context: explains that market and event are mutually required, describes side auto-detection for basket mode, and clarifies how size_usd is interpreted differently between modes (max spend vs target proceeds vs settlement notional). This goes beyond the schema.

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 defines the tool as a realizable-vs-theoretical edge check against live CLOB order book depth. It distinguishes between single-market and basket modes, lists specific return fields, and explicitly ties its use to downstream tools like polymarket_arbitrage and polymarket_edges, making its purpose distinct from siblings.

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?

Explicitly states when to use: 'USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500'. Explains risks of not using it (partial fills lead to unhedged positions). While it does not list explicit alternatives or when-not-to-use, the context strongly implies appropriate use cases.

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

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

Many tools have overlapping purposes, such as multiple ask_pipeworx variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) that differ only subtly, and a large set of prediction market tools (bet_research, polymarket_arbitrage, polymarket_edges, etc.) that can be easily confused. Entity tools like entity_profile, recent_changes, and compare_entities also overlap significantly. An agent would struggle to pick the right tool without careful reading.

Naming Consistency2/5

Tool names mix snake_case (ask_pipeworx, deep_research, forget) and descriptive phrases without a consistent verb_noun pattern. Some start with verbs (compare, generate, scan) while others are nouns or compound phrases (pipeworx_trending, polymarket_fill_risk). This inconsistency makes it hard to predict tool names.

Tool Count2/5

With 35 tools, this MCP server is overly large and covers many diverse domains (data querying, prediction markets, pharmacology, npm scanning, brand visibility, etc.). Typically, a well-scoped server has 5-15 tools; 35 is excessive and suggests a lack of focus, making it unwieldy for an agent to manage.

Completeness2/5

Despite the large number of tools, the server has notable gaps. For example, the pharmacology section only offers search and interaction tools but no create/update/delete. The memory tools are limited to save/recall/forget. Many meta-tools (discover_tools, suggest_questions) exist but add little substance. The server covers many domains superficially rather than providing full lifecycle coverage for any one domain.

Resources