Skip to main content
Glama

Prediction market events

prediction_market_events
Read-only

Track prediction market events and resolutions across Polymarket, Kalshi, and Drift BET. 'upcoming' mode: markets closing soonest with current odds. 'resolved' mode: recently settled markets with outcomes. Cross-platform coverage. Costs $0.005 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
modeNoMode: 'upcoming' (closing soon) or 'resolved' (recently settled)upcoming
limitNoMax results (default: 20)
queryNoFilter by topic
timeframeDaysNoDays to look ahead (upcoming) or back (resolved). Default: 7 upcoming, 30 resolved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the bar is lower. The description adds genuinely useful non-obvious context: the tool is cross-platform and costs $0.005 USDC per call, which affects the agent's decision to invoke it. It does not describe rate limits or pagination, keeping it shy of a 5.

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 purpose, then mode definitions, then the cost warning — a sensible ordering with little waste. The fragment 'Cross-platform coverage.' is slightly redundant with the platform list in the first sentence, but the whole thing is compact.

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?

With no output schema, the description does the right minimal work by indicating what each mode returns (odds, outcomes). Cost is disclosed, which matters for an agent deciding to call. Missing are result-shape details and any pagination or error behavior, so it is not fully complete for a 4-parameter read tool.

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 every parameter is already documented, and the description's mode explanations largely restate the schema. It adds marginal value by clarifying what each mode yields (current odds vs settled outcomes), but nothing about query semantics or how timeframeDays interacts with mode beyond what the schema states.

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?

States a specific verb and resource ('Track prediction market events and resolutions') and names the three platforms covered, plus the two operating modes. It is clear what the tool does, but it never distinguishes itself from nearby siblings like prediction_market_aggregator, prediction_market_odds, or prediction_markets_trending, which overlap heavily.

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 'upcoming' vs 'resolved' distinction gives real guidance on which mode to pick and what each returns. However, there is no guidance on when to choose this tool over the many other prediction-market siblings, nor mention of prerequisites (API key, USDC balance) beyond the price.

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