Loading ToolBench
Real-time prediction market odds from Polymarket and Kalshi. Active markets, probabilities, volume, categories. The betting intelligence layer agents need for event forecasting.
Three tools with complete input schemas and detailed descriptions (194-250 chars each). All parameters are typed with enums where appropriate. Descriptions include use-case guidance and explicit non-use warnings. However, output schemas are documented only in description text, not as formal JSON Schema objects. No tool annotations (readOnlyHint, idempotentHint) present. Error handling guidance is minimal, no recovery paths or actionable error messages defined.
Use this when you need detailed odds, probabilities, and trading data for a specific prediction market. Searches both Polymarket and Kalshi to find the best match by market ID or question text. 1. question: the full prediction market question text 2. outcomes: array of possible outcomes with their current probabilities 3. outcomePrices: decimal probabilities per outcome (0.72 = 72% implied probability) 4. volume: total all-time trading volume in USD 5. volume24h: trading volume in the last 24 hours 6. liquidity: current depth of the order book in USD 7. endDate: resolution date of the market 8. description: detailed market description and resolution criteria 9. active: whether the market is currently open for trading 10. source: which platform the market is from -- "polymarket" or "kalshi" Example output: { question: "Will ETH flip BTC by 2027?", outcomes: ["Yes", "No"], outcomePrices: { "Yes": 0.08, "No": 0.92 }, volume: 2340000, volume24h: 45000, liquidity: 120000, endDate: "2027-12-31", active: true, source: "polymarket" } Use this when a user asks about the probability of a specific event happening, election odds, or crypto predictions. Provides the crowd-sourced probability estimate backed by real money from two leading platforms. Do NOT use for crypto price data -- use token_get_price instead. Do NOT use for crypto news -- use crypto_get_news instead. Do NOT use for stock prices -- use stock_get_quote instead. Do NOT use for DeFi yields -- use defi_find_best_yields instead. Do NOT use for Hyperliquid perp data -- use hyperliquid_get_market_data instead.
Use this when you need to browse active prediction markets or find betting odds on real-world events. Returns a list of active markets from Polymarket and Kalshi with current probabilities, trading volume, and metadata. 1. question: the prediction market question (e.g. "Will Bitcoin reach $100k by December 2026?") 2. outcomePrices: probability for each outcome as decimal (0.65 = 65% chance YES) 3. volume: total trading volume in USD 4. liquidity: current available liquidity in USD 5. endDate: when the market resolves 6. category: topic category (politics, crypto, sports, science, culture) 7. active: whether the market is currently trading 8. source: data source -- "polymarket" or "kalshi" Example output: { markets: [{ question: "Will Trump win 2028?", outcomePrices: { "Yes": 0.42, "No": 0.58 }, volume: 15420000, liquidity: 890000, endDate: "2028-11-06", category: "politics", source: "polymarket" }] } Use this to gauge public consensus on future events. Merges data from both Polymarket (crypto-native) and Kalshi (CFTC-regulated). Essential for research, forecasting, and understanding market sentiment on any topic. Do NOT use for crypto price data -- use token_get_price instead. Do NOT use for crypto news -- use crypto_get_news instead. Do NOT use for stock prices -- use stock_get_quote instead. Do NOT use for DeFi yields -- use defi_find_best_yields instead. Do NOT use for Hyperliquid perp data -- use hyperliquid_get_market_data instead.
Output schemas documented only in description text, not as formal JSON Schema. LLMs cannot parse unstructured output descriptions to infer response structure for downstream tool chaining.
No tool annotations (readOnlyHint, idempotentHint, destructiveHint) present. All three tools are read-only but this is not formally declared in the tool definition.
Error handling lacks recovery guidance. No documented error cases, retryability classification, or actionable error messages. LLMs cannot self-correct on API failures.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 69 | 2025-06-18+ | v2 |
Use this when you need to see what prediction markets are trending right now. Returns the hottest markets from both Polymarket and Kalshi ranked by recent trading volume and activity. 1. question: the market question 2. probability: current implied probability for the leading outcome (decimal) 3. volume24h: trading volume in the last 24 hours in USD 4. totalVolume: all-time trading volume in USD 5. priceChange24h: change in probability over the last 24 hours (e.g. +0.05 = probability rose 5%) 6. category: topic category 7. endDate: when the market resolves 8. source: data source -- "polymarket" or "kalshi" Example output: { trending: [{ question: "Will Fed cut rates in July 2026?", probability: 0.73, volume24h: 890000, totalVolume: 12500000, priceChange24h: 0.08, category: "politics", endDate: "2026-07-31", source: "polymarket" }] } Use this to discover what events the market is most interested in right now. Merges trending data from Polymarket and Kalshi. Great for finding breaking news impact, trending political events, or viral crypto bets. Do NOT use for crypto price data -- use token_get_price instead. Do NOT use for crypto news -- use crypto_get_news instead. Do NOT use for stock prices -- use stock_get_quote instead. Do NOT use for DeFi yields -- use defi_find_best_yields instead. Do NOT use for Hyperliquid perp data -- use hyperliquid_get_market_data instead.
Parameter descriptions lack format/constraint details. 'limit' accepts 1-50 but no min/max bounds declared in schema. 'query' accepts free-form strings with no length or character restrictions documented.
No pagination support documented. Tools returning lists (prediction_list_markets, prediction_trending_markets) lack offset/cursor and total_count fields. Large result sets risk context window exhaustion.