Skip to main content
Glama
predmarket-mcp

predmarket-mcp

search_markets

Read-only

Find open Kalshi and Polymarket prediction markets by keyword, then return each market's ID, title, YES bid/ask/mid, volume, and close time for comparison.

Instructions

Find open markets by keywords, e.g. "fed rate cut december" or "bitcoin 150k".

Returns market id, title, YES bid/ask/mid, volume and close time for each match.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
venueNoboth

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds two genuinely useful traits beyond that: results are restricted to open markets, and each match includes pricing/volume/close-time fields. It omits anything about result caps, ranking/relevance ordering, or cross-venue aggregation behavior.

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?

Two tight sentences: the capability and example queries come first, the return shape second. No filler, no restatement of the tool name, and the examples earn their space by demonstrating query phrasing.

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?

An output schema exists, so the return-value sentence is a bonus rather than a necessity, and the core search behavior is clear. For a three-parameter, multi-venue tool it still leaves meaningful gaps: result limits/pagination, relevance ordering, and what venue="both" actually does to the result set.

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 bears the full burden, and it only covers one of three parameters. The two example queries do clarify query syntax, but limit (default 10) and especially venue (kalshi/polymarket/both, default both) receive no explanation at all — an agent could easily miss that it is searching multiple venues by default.

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 ("Find open markets by keywords") and gives two concrete example queries, which makes the keyword-based nature unambiguous. It implicitly separates itself from get_market (id-based lookup) by describing keyword search, but never names a sibling or contrasts the two explicitly.

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 word "open" scopes the search to non-closed markets and the examples show the expected query style, so usage is implied. However, there is no statement of when to use this versus get_market, compare_venues, or get_recent_trades, and no mention of when-not to use it.

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