Skip to main content
Glama

Surf Prediction Market

surf_prediction_market
Read-only

Track prediction markets on Polymarket and Kalshi with live prices, odds, volume, open interest, trades, and analytics.

Instructions

Use this when the user needs prediction market data from Surf. Track prediction markets on Polymarket and Kalshi. Browse events and markets, view live prices and odds, analyze trading volume and open interest history, inspect individual trades, and discover top-ranked markets by activity.

Commands: analytics - Prediction Market Analytics params: category (string), platform (string) [polymarket, kalshi], time_range (string) [7d, 30d, 90d, 180d, 1y], top_n (integer), sort_by (string) [volume_7d, whale_flow_net_7d, price_change_7d, oi_change_7d], order (string) [asc, desc], limit (integer), offset (integer) correlations - Market Correlations params: category* (string), condition_id (string), min_correlation (number), limit (integer), offset (integer) kalshi-events - Kalshi Events params: event_ticker (string), limit (integer), offset (integer) kalshi-markets - Kalshi Markets params: market_ticker (string), limit (integer), offset (integer) kalshi-open-interest - Kalshi Open Interest History params: ticker* (string), time_range (string) [7d, 30d, 90d, 180d, 1y] kalshi-orderbooks - Kalshi Orderbook History params: ticker* (string), start_time (integer), end_time (integer), limit (integer), pagination_key (string) kalshi-prices - Kalshi Price History params: ticker* (string), time_range (string) [7d, 30d, 90d, 180d, 1y], interval (string) [1h, 1d, latest] kalshi-trades - Kalshi Trades params: ticker* (string), taker_side (string) [yes, no], min_amount (integer), from (string), to (string), sort_by (string) [timestamp, notional_volume_usd], order (string) [asc, desc], limit (integer), offset (integer) kalshi-volumes - Kalshi Volume History params: ticker* (string), time_range (string) [7d, 30d, 90d, 180d, 1y] matching-market-daily - Cross-Platform Daily Comparison (Polymarket <> Kalshi) params: polymarket_condition_id* (string), kalshi_market_ticker* (string), time_range (string), limit (integer), offset (integer) matching-market-pairs - Cross-Platform Prediction Market Matcher (Polymarket <> Kalshi) params: category (string), match_type (string) [exact, related], active_only (boolean), min_confidence (integer), polymarket_condition_id (string), kalshi_market_ticker (string), sort_by (string) [confidence, polymarket_volume, kalshi_volume, spread_pct], order (string) [asc, desc], limit (integer), offset (integer) polymarket-events - Polymarket Events params: event_slug* (string), limit (integer), offset (integer) polymarket-leaderboard - Polymarket Leaderboard params: sort_by (string) [pnl, volume, trade_count], order (string) [asc, desc], limit (integer), offset (integer) polymarket-markets - Polymarket Markets params: market_slug* (string), limit (integer), offset (integer) polymarket-open-interest - Polymarket Open Interest History params: condition_id* (string), time_range (string) [7d, 30d, 90d, 180d, 1y] polymarket-orderbooks - Polymarket Orderbook History params: token_id* (string), start_time (integer), end_time (integer), limit (integer), pagination_key (string) polymarket-positions - Polymarket Wallet Positions params: address* (string), limit (integer), offset (integer) polymarket-price-ohlcv - Polymarket OHLCV Candlesticks params: condition_id* (string), start_time (integer), end_time (integer), interval (integer) polymarket-prices - Polymarket Price History params: condition_id* (string), time_range (string) [7d, 30d, 90d, 180d, 1y], interval (string) [1h, 1d, latest] polymarket-smart-money - Polymarket Smart Money params: view (string) [positioning, trades], condition_id (string), category (string), direction (string) [bullish, bearish, neutral], whale_tier (string) [whale, large, mega], from (string), to (string), sort_by (string) [smart_wallets_involved, smart_buy_volume_usd, smart_sell_volume_usd, amount_usd, block_time], order (string) [asc, desc], limit (integer), offset (integer) polymarket-trades - Polymarket Trades params: condition_id (string), address (string), type (string) [trade, redemption, all], outcome_label (string) [Yes, No], min_amount (number), from (string), to (string), sort_by (string) [timestamp, notional_volume_usd], limit (integer), offset (integer) polymarket-volume-split - Polymarket Volume Split (YES/NO) params: condition_id* (string), granularity (string) [hour, day, week], start_time (integer), end_time (integer) polymarket-volumes - Polymarket Volume History params: condition_id (string), token_id (string), time_range (string) [7d, 30d, 90d, 180d, 1y], interval (string) [1h, 1d], granularity (string) [day, week, month, year, all], start_time (integer), end_time (integer)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsNo
commandYes
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds scope (what data is accessible) but does not disclose additional behavioral aspects such as rate limits, pagination behavior, data freshness, or any side effects. It is consistent with annotations, so no contradiction.

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?

The description is long but well-structured as a command reference with consistent formatting and a clear opening purpose statement. Each command line provides necessary parameter information, so length is justified by the tool's 23 subcommands. It is not overly verbose for the complexity it covers.

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?

Given the tool's complexity (23 commands) and minimal schema/annotations, the description provides substantial parameter details and clearly enumerates all available operations. It lacks examples of response structures or workflow guidance, but the command names and parameter lists suffice for basic selection and invocation. The absence of an output schema means return values are not required to be explained.

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 input schema only has a generic 'params' object and a command enum, providing zero parameter-level documentation. The description compensates by listing each command's expected parameters with types and allowed enums (e.g., platform, time_range, sort_by), and marks required parameters with *, enabling an agent to construct valid calls despite the schema being underspecified.

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?

The description clearly identifies the tool as providing prediction market data for Polymarket and Kalshi, with specific actions like browsing events/markets, viewing prices/odds, and analyzing volume/open interest. This distinguishes it from sibling tools focused on other domains (e.g., surf_dex, surf_exchange) by naming a specific resource and scope.

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?

The opening sentence explicitly states 'Use this when the user needs prediction market data from Surf,' providing a clear usage context. However, it does not directly mention alternatives or when not to use the tool, though the command list internally guides between Polymarket and Kalshi subcommands.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/asksurf-ai/surf-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server