Chargebee

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

Name	Required	Description
`limit`	No	Top N edges to return after ranking. Default 10, max 25.
`window`	No	Polymarket volume window to filter markets. Default 1wk.
`min_kelly`	No	Minimum 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_pp`	No	Minimum \|edge\| in percentage points to include (default 0.5). Edge is evaluated NET of slippage.
`slippage_pp`	No	Assumed 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_pp`	No	Tradeable-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_liquidity`	No	Tradeable-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_filter`	No	Comma-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_kelly`	No	Minimum 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.

Changed2 schema fields changedMay 27, 2026

addedInput schema / properties / max_spread_pp

Added value: +{
+  "description": "Tradeable-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.",
+  "type": "number"
+}

addedInput schema / properties / min_liquidity

Added value: +{
+  "description": "Tradeable-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.",
+  "type": "number"
+}

Changed1 schema field changedMay 26, 2026

addedInput schema / properties / min_partition_leg_kelly

Added value: +{
+  "description": "Minimum 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.",
+  "type": "number"
+}

Changed4 schema fields changedMay 24, 2026

addedInput schema / properties / category_filter

Added value: +{
+  "description": "Comma-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.",
+  "type": "string"
+}

changedInput schema / properties / min_edge_pp / description

Previous value: -"Minimum |edge| in percentage points to include (default 0.5)."New value: +"Minimum |edge| in percentage points to include (default 0.5). Edge is evaluated NET of slippage."

addedInput schema / properties / min_kelly

Added value: +{
+  "description": "Minimum 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.",
+  "type": "number"
+}

addedInput schema / properties / slippage_pp

Added value: +{
+  "description": "Assumed 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.",
+  "type": "number"
+}

AddedMay 18, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations provide readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds detailed context: caching (1h at KV level), edge calculation methodology, model families, knobs, and response structure. 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.

Conciseness4/5

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

The description is long but well-structured with sections and bullet points. Every sentence adds useful information for an agent to understand edge computation and parameters. Slightly verbose but not wasteful.

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?

No output schema exists, but the description thoroughly explains the response structure (by_segment, fed_candidates, _diagnostics) and all edge fields. It is complete for a complex tool with 9 parameters and multiple segments.

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 meaning beyond field names, e.g., explaining why min_kelly doesn't filter partition arbs and how min_partition_leg_kelly applies. This helps the agent understand parameter interactions.

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 starts with a specific verb+resource: 'Scan top Polymarket markets and return opportunities where Pipeworx data disagrees with market price.' It clearly states the tool's purpose and distinguishes from siblings like polymarket_arbitrage, polymarket_edge_tracker, etc.

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 says it is 'Built for "what should I bet on today" — agents discover opportunities without paging hundreds of markets.' It explains tradeable-edge knobs and how to use them, but does not explicitly state when not to use this tool or compare it to alternatives.

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

All Chargebee tools Inspect

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

B3.3/5.0

Disambiguation1/5

Multiple tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all answer questions or discover data via the same routing engine, with ask_pipeworx_beta explicitly stated to be identical to ask_pipeworx. Polymarket tools (arbitrage, edges, edge_tracker, fill_risk) also blur together, and ai_visibility_check overlaps with scan_competitor_ai_presence.

Naming Consistency2/5

Some clusters are consistent (chargebee_list_*/chargebee_get_*, polymarket_*, pipeworx_*), but the set mixes snake_case with varying verb styles and many unprefixed tools (remember, recall, forget, subscribe, unsubscribe, validate_claim). The 5 Chargebee tools use a clean prefix while the other 31 tools follow several different conventions, making the overall pattern unpredictable.

Tool Count2/5

36 tools is excessively heavy for a server named Chargebee, especially since only 5 tools actually relate to Chargebee. The remaining 31 tools form a broad Pipeworx/prediction-market/utility toolkit that has little connection to the server's apparent billing purpose, making the count feel bloated and unfocused.

Completeness1/5

The Chargebee-specific surface is severely incomplete: it only supports reading customers, subscriptions, and invoices, with no create, update, delete, payment, dunning, coupon, or plan-management operations. The rest of the tools belong to unrelated domains, so the set as a whole has no coherent lifecycle coverage and would leave agents unable to perform even basic Chargebee management tasks.

Polymarket Edges

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources