Skip to main content
Glama

Polymarket, Kalshi, Hyperliquid Funding Arbitrage & DEX Swap MCP

Scan Kalshi & Polymarket Prediction Odds

scan_prediction_market_odds
Read-onlyIdempotent

Fetches live macro, crypto, and policy implied YES probabilities across Kalshi (CFTC) and Polymarket (CLOB), including matched cross-venue gaps.

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": "scan_prediction_market_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety and idempotency profile is fully covered. The description adds genuinely new context: it aggregates across two named venues and returns 'matched cross-venue gaps', telling the agent what the output contains. It does not disclose auth requirements (Kalshi vs Polymarket access differ), rate limits, caching/freshness window, or what happens when one venue is unavailable.

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?

A single sentence with no filler, front-loading the verb and the data scope, then appending the venue detail and the cross-venue gap capability as parentheticals. Every clause carries information an agent would otherwise have to guess.

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 parameters, no output schema, and rich annotations, the description only needs to convey what comes back and from where, which it does via 'implied YES probabilities' and 'matched cross-venue gaps'. The remaining gap is operational: no indication of freshness, coverage breadth, or degradation behavior when a venue is down.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing in the schema for the description to clarify. The description implicitly confirms this is a broad, unfiltered scan rather than a targeted query, which is the only parameter-relevant signal available.

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 concrete verb ('Fetches') plus the exact resource: implied YES probabilities across Kalshi and Polymarket, scoped to macro, crypto, and policy markets. The prediction-market domain is unmistakably distinct from the sibling tools (perp funding spreads, kimchi premium, Pendle, stable yields, bridge quotes), so an agent can select it without opening the schema.

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 by the domain vocabulary rather than stated: an agent can infer this is the tool for prediction-market implied probabilities, and 'live' hints at real-time freshness checks. However, there is no explicit when-to-use, when-not-to-use, or routing statement toward or away from any alternative.

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.