Skip to main content
Glama

Shodan

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?

Annotations already indicate readOnlyHint=true and non-destructive, but the description adds rich behavioral context: it walks the order-book ladder, returns fill metrics, and warns about the dominant loss mode (partial basket fills causing unhedged directional positions). No contradiction with 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 packed with information and uses formatting to highlight key points. It is somewhat long but well-organized, front-loading the purpose and structure. Every sentence earns its place.

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?

Without an output schema, the description thoroughly details return fields for both modes (top_of_book, vwap_fill_price, slippage_pp, theoretical_sum, capture_ratio, thin_legs, forced_directional_risk, etc.), covering edge cases and risks comprehensively.

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 description coverage is 100%, but the description adds extra meaning: for size_usd it clarifies settlement notional in basket mode and default/clamp; for side it explains auto behavior. This adds value 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?

The description clearly states it performs a 'Realizable-vs-theoretical edge check against live CLOB order-book depth.' It distinguishes between single-market and basket modes, and references sibling tools like polymarket_arbitrage and polymarket_edges for differentiation.

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 states 'REQUIRES one of `market` or `event`' and advises 'USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500,' explaining the risk of partial basket fills converting an arb into an unhedged directional position.

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

All Shodan 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 server name 'Shodan' misleadingly implies a narrow focus on network security scanning, yet the tool set includes many unrelated tools for data lookup (ask_pipeworx, deep_research, etc.), memory management, and subscriptions. Within the pipeworx tools, there is overlap between ask_pipeworx, ask_pipeworx_grounded, and deep_research, which can confuse agents about which to choose.

Naming Consistency2/5

Tool names mix conventions: some use underscores (ai_visibility_check, shodan_host), others use lowercased phrases without clear partitioning (ask_pipeworx, deep_research, entity_profile). Verb-noun patterns are inconsistent (e.g., 'scan_competitor_ai_presence' vs 'compare_entities'). This lack of a predictable naming scheme increases cognitive load.

Tool Count2/5

With 33 tools covering distinct domains (Shodan scanning, pipeworx data, memory, subscriptions), the server feels overloaded and unfocused. While each tool may individually be useful, the bundling contradicts the principle of a single-purpose server. A more appropriate count for a focused Shodan server would be under 10 tools.

Completeness2/5

For the Shodan domain, only three tools are provided (host, host_count, host_search), missing key capabilities like DNS lookups, vulnerability search, or API key management. The pipeworx tool set is extensive but not the server's advertised purpose, leaving gaps in both areas. The addition of memory and subscription tools adds unrelated functionality without completing any single domain.

Resources