Skip to main content
Glama

Prediction market aggregator

prediction_market_aggregator
Read-only

Cross-platform prediction market search. Queries Polymarket, Kalshi, and Drift BET in parallel and returns unified results sorted by volume. Finds the same event across platforms to compare odds and spot arbitrage opportunities. Returns probabilities, volume, liquidity, and cross-platform matches with probability spreads. Costs $0.01 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "prediction_market_aggregator"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return across all platforms (default: 20)
queryYesSearch query — topic, keyword, or question (e.g. 'bitcoin', 'election', 'fed rate cut', 'world cup')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only cover readOnlyHint and openWorldHint; the description adds genuinely new behavioral context: it fans out to three upstream venues in parallel, ranks by volume, and — most valuably — discloses a $0.01 USDC per-call cost, which no structured field carries. It omits latency expectations, per-platform failure/partial-result behavior, and pagination, which keeps it off 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.

Conciseness5/5

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

Four short sentences, front-loaded with the what and then the why, then the return shape, then cost. Nothing is redundant with the title and every sentence carries distinct information.

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 correctly compensates by enumerating return fields (probabilities, volume, liquidity, cross-platform matches with spreads) and the cost. For an open-world aggregator it would ideally mention what happens when a platform returns nothing or how partial coverage is signaled, but nothing essential to making the call is missing.

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% with only two simple parameters, both fully documented in-schema, so the baseline is 3. The description adds a little context in that 'sorted by volume' hints at how results are ranked and the examples question the scope of `query`, but it adds no syntax or format guidance 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?

States a specific verb and resource — 'Cross-platform prediction market search' — and names the exact three platforms queried (Polymarket, Kalshi, Drift BET). The word 'cross-platform' plus the parallel-query detail cleanly separates it from single-venue siblings like polymarket_quote and from prediction_market_events.

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?

'Finds the same event across platforms to compare odds and spot arbitrage opportunities' gives a clear use case and implicitly routes arbitrage intent here. It stops short of explicit exclusions or naming competing siblings such as prediction_market_arbitrage, so an agent must infer the boundary rather than being told it.

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