Skip to main content
Glama

Prediction arb

prediction_arb
Read-onlyIdempotent

Live cross-venue Polymarket vs Kalshi prediction-market arbitrage & mispricing scanner: matches equivalent open events, reports mid-probability divergence bps, and checks exact cross-venue Dutch-book cost (YES_A + NO_B < $1.00). $0.005 per call over x402 or X-API-Key. Not advice.

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_arb"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOptional topic filter (e.g. fed, election, bitcoin).
limitNoMax matched pairs (default 15, max 30).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).
minScoreNoMinimum match score 0.1-1.0 (default 0.32).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, and the description adds real context beyond them: per-call cost of $0.005, two payment paths (x402 or X-API-Key), and the substance of what is computed (divergence bps, YES_A + NO_B < $1.00 Dutch-book test). It does not disclose latency, refresh cadence, or whether unmatched events are dropped, which keeps it from a 5.

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 core capability is front-loaded in the first sentence, followed by pricing, auth options, and a one-line disclaimer. Every sentence carries information, though the first sentence is dense with jargon (bps, Dutch-book, mid-probability) that may slow parsing.

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?

With no output schema, the description must convey what comes back, and it does: matched pairs, mid-probability divergence in bps, and exact cross-venue Dutch-book cost. Combined with annotations covering safety and the fully documented schema, an agent has everything needed to decide and call correctly.

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 coverage is 100%, so every parameter is already documented in the schema, which sets the baseline at 3. The description adds only marginal meaning, mainly that matching is score-based (loosely tied to minScore) and that topic filtering targets equivalent open events. It gives no extra detail on the payment payload or limit behavior.

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?

The description names a specific verb-and-resource combination: a cross-venue arbitrage and mispricing scanner covering Polymarket vs Kalshi. It spells out the three concrete operations (event matching, mid-probability divergence in bps, Dutch-book cost check), so an agent can tell this apart from a generic odds or movers tool. It stops short of naming sibling tools like prediction_odds or prediction_movers as the non-arbitrage alternatives.

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 only implied: an agent can infer this is for finding cross-venue arbitrage or mispricing rather than raw prices. There is no explicit when-to-use or when-not-to-use guidance, and no pointer to the sibling tools an agent should choose for plain odds or price-movement queries. The 'Not advice' note is a disclaimer, not routing guidance.

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