Skip to main content
Glama

Securitytrails

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

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

Annotations already declare readOnlyHint=true, destructiveHint=false, etc., so the safety profile is clear. The description adds detailed behavioral context: walks the order book ladder, returns slippage, fill details, and risk warnings about thin books and partial fills. Enhances transparency beyond 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 lengthy but well-structured with clear sections and all-caps emphasis. Every sentence serves a purpose, though it could be slightly more concise. Front-loaded with purpose and mode distinction.

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 complexity (two modes, multiple return fields, no output schema), the description is thorough: explains both modes, key return fields, risk of partial fills, and usage prerequisites. Completely covers what an agent needs to use effectively.

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% with basic parameter meanings. The description adds extra semantics: clarifies size_usd for basket mode as settlement notional, and explains side default behavior for basket. 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 the tool checks realizable vs theoretical edge against live order book depth, distinguishes between single-market and basket modes, and mentions specific return fields. It differentiates itself from siblings by explicitly stating when to use it before polymarket_arbitrage or polymarket_edges trades.

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 edges trades above ~$500. It explains why (theoretical overround not capturable, partial fills cause directional risk) and gives mode selection criteria.

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

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

Multiple tools occupy the same general query/research space: ask_pipeworx, ask_pipeworx_beta (currently identical), ask_pipeworx_grounded, deep_research, validate_claim, entity_profile, and recent_changes all overlap in what they can return. The descriptions are detailed and try to steer usage, but the boundaries are fuzzy enough that agents can easily select the wrong tool.

Naming Consistency3/5

All names are snake_case and descriptive, but there is no consistent verb_noun convention across the set. It mixes bare verbs (remember, recall, forget), noun phrases (entity_profile, recent_changes), domain-prefixed families (securitytrails_*, polymarket_*), and Pipeworx meta-tools (ask_pipeworx_*), so the pattern is predictable only within each family.

Tool Count2/5

35 tools is above the 25+ threshold for a coherent MCP surface, and many are highly specialized (Polymarket arbitrage, AI visibility checks, npm dependency scans) rather than core Securitytrails functionality. The set feels like multiple products merged into one rather than a well-scoped toolset.

Completeness3/5

The broad data-research workflows are well covered: routing, entity resolution, profiling, comparison, validation, subscriptions, memory, and basic Securitytrails domain lookups. But for a server named Securitytrails, there are obvious missing security-intelligence operations such as associated domains, IP/certificate enrichment, and broader DNS infrastructure enumeration.

Resources