Realtap

Prediction markets and their odds

list_prediction_markets

Read-onlyIdempotent

Prediction markets on Cardano (Bodega Market), read from the chain: each market's question, the probability its automated market maker currently gives YES and NO (percent), when trading ends, the funds in the market, traded volume and, once published, the outcome. Use it for "what are the odds of …" or "which prediction markets are open" questions. Amounts are in the market's payment token (ADA unless paymentToken says otherwise). Outcomes are published on chain by the Bodega team, not by a decentralised oracle; most markets are sports events. Odds are a market price, not a forecast you should present as fact: name the source and the time.

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

Input Schema

Name	Required	Description	Default
`sort`	No	Ordering. Default: deadline (soonest first for open markets, latest first otherwise). volume = all-time traded volume; activity = most recently traded.
`limit`	No	How many markets to return (1-50, default 15).
`query`	No	Only markets whose question contains this text.
`status`	No	open = trading now; awaiting = trading ended, no result published yet; resolved = result published, winners can claim; closed = wound up.	open

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations, it discloses that data is read from chain, that amounts are denominated in the market's payment token, that outcomes are published by the Bodega team rather than a decentralized oracle, and that odds are market prices rather than forecasts. These are important behavioral and interpretation details not captured by readOnly/openWorld annotations.

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?

The description is front-loaded with the resource and returned fields, followed by usage guidance and interpretive caveats. Every sentence adds value for an agent that must answer prediction-market questions responsibly.

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?

There is no output schema, but the description effectively explains the return values: question text, YES/NO probabilities, deadline, funds, volume, and outcome. Combined with annotations covering safety and idempotency, it gives an agent enough context to call and interpret the tool 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 description coverage is 100%, and all four parameters already have clear enum/default documentation in the schema. The description adds domain context about payment tokens and outcomes, but does not materially clarify the sort, limit, query, or status parameters beyond what the schema provides.

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 states a specific verb and resource: listing prediction markets on Cardano/Bodega Market, and enumerates the returned fields (question, YES/NO odds, deadline, funds, volume, outcome). It is clear enough to distinguish it from generic market tools, but it does not explicitly name or differentiate itself from the sibling get_prediction_market singular lookup.

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?

It gives concrete usage contexts: questions like "what are the odds of …" and "which prediction markets are open." However, it does not state when not to use it or explicitly route agents to alternatives such as get_prediction_market for a single market.

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

All Realtap tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?