Skip to main content
Glama

Polymarket prediction odds (x402)

prediction_market_odds

Read-onlyIdempotent

$0.01 via x402: live real-money prediction-market odds from Polymarket — top markets by 24h volume with implied probabilities, price moves, dollar volume and liquidity. Search by keyword (bitcoin, election, fed, world cup, AI). For trading, forecasting, news and event-resolution agents. One call instead of integrating the exchange API.

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

Input Schema

NameRequiredDescriptionDefault
qNoKeyword filter, e.g. bitcoin, election, fed
topNo1-25, default 10
sortNovolume|liquidity, default volume
x_paymentNoOptional signed x402 payment payload

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 already declare readOnly, idempotent, and open-world, so the bar is lower; the description adds real value by disclosing a cost ('$0.01 via x402') and that payment payload may be required, plus that data is live and exchange-sourced. It does not mention rate limits, caching/freshness windows, or failure behavior when payment is missing.

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?

Front-loaded with the resource and scope, then use cases, then the value proposition; every clause carries information. The closing line ('One call instead of integrating the exchange API') is mildly promotional but still justifies choosing this tool over direct integration.

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 still enumerates the returned fields (implied probabilities, price moves, dollar volume, liquidity), all four params are schema-documented, and annotations cover the safety profile. Nothing essential for a correct call appears 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 coverage is 100%, so q/top/sort/x_payment are already documented; the description mostly restates the keyword filter with extra example terms and mentions volume implicitly via 'top markets by 24h volume'. The sort enum ('volume|liquidity') and the 1-25 bound on top are not elaborated 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 resource ('live real-money prediction-market odds from Polymarket') plus scope ('top markets by 24h volume') and the payload returned (implied probabilities, price moves, dollar volume, liquidity). This clearly distinguishes it from sibling tools covering crypto metrics, perps, FX, and macro indicators.

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?

Gives concrete use contexts ('for trading, forecasting, news and event-resolution agents') and search examples ('bitcoin, election, fed, world cup, AI'), which tells an agent when this tool fits. It stops short of explicit exclusions or naming an alternative tool when prediction-market data isn't wanted.

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