Skip to main content
Glama
GMPSignal MCP Server

GMPSignal MCP Server

query_prediction_market_odds

Read-onlyIdempotent

Query real-time implied probabilities, Yes/No prices, trading volume, liquidity, and cross-venue arbitrage spreads across Polymarket, Kalshi, and Manifold to compare prediction market odds.

Instructions

Query real-time implied probabilities, Yes/No contract prices, 24h trading volume, order book liquidity, and cross-venue arbitrage spreads across Polymarket, Kalshi, and Manifold Markets.

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": {
      "sources": "<sources>"
    },
    "name": "query_prediction_market_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordNoOptional topic or event keyword filter (e.g., "Fed", "Bitcoin", "Election").
sourcesYesPrediction market exchanges to query.
maxResultsNoMaximum number of prediction market contracts to return.
minVolumeUsdNoMinimum total market trading volume in USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.2

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds value by specifying 'real-time' freshness and describing the returned fields (probabilities, prices, volume, liquidity, arbitrage spreads). It doesn't mention any rate limits, latency, or how venues are aggregated, so a 3 is appropriate.

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?

It is a single, front-loaded sentence that names the verb, the data fields, and the venues with no filler. Every clause adds information an agent needs to decide whether to call it.

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?

For a simple four-parameter read tool with no output schema, the description tells the agent what data is returned and from which venues, which is most of what is needed. It doesn't explain behavior when a requested venue is unavailable or how results are merged across venues, which would be needed to reach a 5.

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%, and each of the four parameters (keyword, sources, maxResults, minVolumeUsd) is documented in the schema with types, defaults, and bounds. The description adds no parameter-level detail beyond the venue list, which matches the schema's sources enum. Baseline 3 is correct because the schema does all the heavy lifting.

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 has a specific verb ('Query') and enumerates the exact resource: implied probabilities, Yes/No contract prices, 24h volume, order book liquidity, and cross-venue arbitrage spreads across Polymarket, Kalshi, and Manifold. That is far more specific than a generic 'get market data' and makes the tool easy to identify. It stops short of a 5 because it never contrasts itself with a related tool such as analyze_crypto_orderbook_arbitrage, so the agent must infer that this covers prediction markets specifically.

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?

The description implies when the tool is useful (when an agent needs real-time market-implied probabilities or arbitrage spreads), but it never states when to use this instead of a sibling, nor any exclusions or prerequisites. For example, it doesn't say whether to use this instead of a regional-markets query. Usage guidance is therefore only implied, not explicit.

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