Skip to main content
Glama

Abn Lookup

by io.github.pipeworx-io

Polymarket Edges

polymarket_edges
Read-onlyIdempotent

Scan top Polymarket markets and return opportunities where Pipeworx data disagrees with market price. Built for "what should I bet on today" — agents discover opportunities without paging hundreds of markets. FIVE MODEL FAMILIES grouped into three response segments under by_segment: (1) MODEL_DRIVEN — crypto_price (lognormal barrier from 90d FRED log-returns) and news_momentum (GDELT 7d/21d article-volume ratio, soft signal w/ halved Kelly). (2) STRUCTURAL_ARBITRAGE — partition_overround on mutually-exclusive events; per-leg favorite-longshot bias correction with per-sport α (tennis 1.02, soccer 1.10, MMA 1.15, default 1.0); placeholder-slug filter drops will-person-X / will-team-Y / will-manager-Z / will-someone-else- backstops; partitions with >20% placeholder fraction skipped entirely. (3) CONCENTRATED_LONGSHOT — basket trade when one leg ≥75% AND ≥2 longshots ≤8% AND portfolio return ≥25:1; rare-by-design (gates relaxed Run 8 from prior 85%/5%/50:1). EVERY OPPORTUNITY carries edge_pp_net (after slippage), kelly_fraction + kelly_fraction_half (capped at 0.25), market.liquidity, market.spread_pp, market.volume, plus a 24h-move warning ("Market moved X.Xpp in 24h") when the recent move alone exceeds the edge — your edge may already be in the price. TRADEABLE-EDGE KNOBS: min_liquidity / max_spread_pp drop opportunities where edge isn't realizable; min_partition_leg_kelly filters partitions by best per-leg Kelly. RESPONSE TOP-LEVEL: by_segment{model_driven,structural_arbitrage,concentrated_longshot}, fed_candidates/fed_note (Fed bets surface here, excluded from ranking — 1m-T vs EFFR signal is unreliable at meeting-month horizons without paid OIS/SOFR-futures data), and _diagnostics{concentrated_longshot:{...funnel counters},category_counts,filter_skips} so callers can see WHY a segment is empty (top-N stale, all candidates failed gates, knob dropped them). Cached 1h at the KV level keyed on all knobs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoTop N edges to return after ranking. Default 10, max 25.
windowNoPolymarket volume window to filter markets. Default 1wk.
min_kellyNoMinimum half-Kelly fraction (as decimal, e.g. 0.005 = 0.5% of bankroll) to include single-leg opportunities. Default 0 (no filter). Skips opportunities that are too small to bet sensibly even if the edge is large.
min_edge_ppNoMinimum |edge| in percentage points to include (default 0.5). Edge is evaluated NET of slippage.
slippage_ppNoAssumed execution slippage in percentage points per leg (default 0.3). Subtracted from raw |edge| before ranking and Kelly sizing. Polymarket has zero trading fees as of 2024 but bid/ask + thin depth typically eats 20-50bp per trade. Bump for very thin partitions; drop to 0 if you have a smarter fill model.
max_spread_ppNoTradeable-edge filter. Maximum bid/ask spread in percentage points on the representative market. Default null (no filter). Set to 2 to require tight books — anything wider eats most plausible edges.
min_liquidityNoTradeable-edge filter. Minimum $ liquidity on the representative market (or for partition_overround, on at least one top_leg). Default 0 (no filter). Set to 5000 to drop thin-book opportunities where executing the edge would walk the book past breakeven.
category_filterNoComma-separated list to restrict the output: "model_driven" (crypto_price + news_momentum), "structural_arbitrage" (partition_overround), "concentrated_longshot". Combine like "model_driven,structural_arbitrage". Default: all.
min_partition_leg_kellyNoMinimum BEST per-leg half-Kelly fraction across a partition_overround opportunity's top_legs (or longshot_basket legs). Default 0 (no filter). Partition arbs always return kelly_fraction_half=0 at the parent level by design (basket trades don't compose to single-leg Kelly), so min_kelly never filters them — this knob applies to the per-leg Kelly inside top_legs instead. Use to suppress thin partitions whose individual leg edges aren't worth the per-leg slippage cost.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark this as readOnly, idempotent, and non-destructive. The description goes well beyond them by disclosing caching behavior ('Cached 1h at the KV level keyed on all knobs'), diagnostics output (_diagnostics with funnel counters), the 24h-move warning, slippage assumptions, and the caveat that the edge may already be priced in. This is rich, honest behavioral context with no 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 and dense, but the tool is genuinely complex: five model families, three response segments, multiple filter knobs, diagnostics, and caching behavior. It is front-loaded with purpose and uses caps, numbering, and grouped sections to aid scanning. A more compact version would risk losing important caveats and segment semantics.

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 there is no output schema, the description compensates well by documenting the top-level response shape (by_segment, fed_candidates/fed_note, _diagnostics), the per-opportunity fields (edge_pp_net, kelly_fraction, liquidity, spread_pp, volume), and the caveats that explain empty results. For a complex 9-parameter discovery tool with no required arguments and no output schema, this is unusually complete.

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?

Input schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by grouping knobs into 'TRADEABLE-EDGE KNOBS' and explaining nuanced interaction, e.g. min_kelly never filters partition arbs because parent-level kelly_fraction_half is 0 by design, while min_partition_leg_kelly applies per-leg instead. This is genuinely useful semantic context, though much parameter detail already lives in 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 states a specific verb and resource ('Scan top Polymarket markets and return opportunities where Pipeworx data disagrees with market price') and frames the intended use case ('what should I bet on today'). It names the three response segments and model families, making the tool's scope concrete and distinguishable from siblings like polymarket_arbitrage.

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 gives clear context for when to use the tool: discovering today's betting opportunities without paging hundreds of markets. It also explains what is excluded (Fed bets from ranking) and why. It does not explicitly name sibling alternatives or state when to prefer a different tool, but the use-case framing is strong enough to guide an agent.

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

All Abn Lookup 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

Several tools have unclear or overlapping boundaries: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, while ask_pipeworx, deep_research, and validate_claim all handle factual lookup/research tasks. The five polymarket_* tools plus bet_research also overlap enough that an agent could easily pick the wrong entry point despite verbose descriptions.

Naming Consistency3/5

All names are snake_case and generally descriptive, but conventions are mixed: some are verb-first (ask_pipeworx, resolve_entity, validate_claim), some are noun-first (abn_lookup, entity_profile, polymarket_edges), and prefixes like pipeworx_ and polymarket_ are used inconsistently. It is readable but not a clean, predictable pattern.

Tool Count2/5

34 tools is far too many for a server named 'Abn Lookup' — most of the surface is a broad data-research platform with prediction-market analysis, memory, subscriptions, feedback, and web utilities. The count could fit a large platform, but under this server name and with several near-duplicate entry points, it feels bloated.

Completeness4/5

For a read-only lookup/research server, coverage is strong: ABR lookups, entity resolution, single-query research, grounded verification, deep research, company profiles, comparisons, change feeds, prediction-market analysis, memory, and subscriptions are all represented. Minor gaps exist (e.g., no ACN search-by-name, no order execution), but no core workflow dead-ends.

Resources