Skip to main content
Glama

Microverse Market Data

Search prediction markets

search_prediction_markets
Read-onlyIdempotent

Search Kalshi event contracts and Polymarket markets by text (e.g. 'bitcoin', 'election', 'Fed'). Returns tickers with titles, strikes/outcomes, close times and live best bid/ask (probability, 0-1). Use get_order_book(venue, ticker) for the full book.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_prediction_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
venueNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds genuinely useful behavior: it discloses the return payload (tickers, titles, strikes/outcomes, close times, live best bid/ask) and the important convention that prices are probabilities on a 0-1 scale. It omits any note on coverage breadth, rate limits, or what happens when a query matches nothing.

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?

Three sentences, front-loaded with purpose, then return shape, then the hand-off to the sibling. No redundant restatement of the title or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only search with no output schema, describing the return fields is the right call and is done well. However, with three undocumented parameters and no output schema, the definition leaves the agent guessing about the venue selector and result cap, which materially affects how the tool should be invoked.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It explains the required query well with examples and implies venue by naming two exchanges, but never explains the venue values ('all' default, per-exchange selection) and says nothing about limit (default 50) or how many results are returned per page.

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 verb (Search) plus the exact resources (Kalshi event contracts and Polymarket markets) and the search dimension (by text), with concrete query examples. An agent can immediately distinguish this from get_order_book or get_historical_book.

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?

Explicitly routes the agent to get_order_book(venue, ticker) when the full book is needed, which is the key boundary for this tool. It gives no guidance on when to prefer compare_venues or list_symbols, and no exclusions for cases where search is the wrong entry point.

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