Skip to main content
Glama

Prediction market arbitrage

prediction_market_arbitrage
Read-only

Find prediction market arbitrage opportunities across Polymarket, Kalshi, and Drift BET. Compares odds for the same event across platforms, calculates probability spreads, and flags actionable opportunities (>3% spread). Sorted by biggest spread first. Costs $0.01 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "prediction_market_arbitrage"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default: 15)
queryNoFilter by topic (e.g. 'bitcoin', 'election', 'fed')
minSpreadPctNoMinimum probability spread % to include (default: 2.0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations: readOnlyHint and openWorldHint already cover safety, and the description adds the paid-call cost ($0.01 USDC per call), the result ordering (biggest spread first), and the actionable threshold. It does not disclose odds freshness/latency or whether all three venues are always queried successfully, which matters for an arbitrage decision.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Four short sentences, zero filler, front-loaded with the platform scope and outcome, then the calculation method, then the sort order and price. Each sentence carries information an agent needs; the cost note earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description does most of the work by stating the result shape is spread-sorted opportunities above a threshold. It stops short of describing what an opportunity record contains (venues, prices per side, liquidity) or how venue coverage affects results, leaving a modest gap for a data-returning tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3 and the schema already explains limit, query, and minSpreadPct. The description does not add syntax or semantics for any parameter, and it introduces a mild inconsistency by advertising a '>3% spread' actionability threshold while minSpreadPct defaults to 2.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb+resource: 'Find prediction market arbitrage opportunities' with the three platforms (Polymarket, Kalshi, Drift BET) named, plus the mechanism (compares odds, calculates spreads). It implicitly separates itself from prediction_market_odds and prediction_market_aggregator by scoping to cross-platform spread detection, but never names a sibling or states the distinction explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer this is the tool for cross-venue arbitrage and that prediction_market_odds/aggregator serve single-venue or broader queries, but there is no when/when-not guidance and no named alternative. The '>3% actionable' framing gives a filtering context, which helps, but it is not a routing rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources