Skip to main content
Glama

KalshiSpy

Search Kalshi markets by title or keywords

search_markets
Read-only

Find Kalshi markets by title or keywords, the way the KalshiSpy app's search works (a team, a nickname or an approximate title works). WITHOUT an API key it returns SETTLED WINS ONLY: settled markets where KalshiSpy's roster of ID-verified, high-profit Kalshi traders held the winning side (wins only, never a hit rate). WITH an Elite or Lifetime API key the same call also returns OPEN markets in open_markets: roster positions and named traders' recent trades on still-open markets, and it costs 1 unit of the daily quota. Always read data.access: it says which answer you got and, when a key was refused, why; relay that sentence rather than guessing. Call this first whenever the user names a market in words, send the words under the argument name this tool's own schema gives, and cite each market's kalshi_url. An empty list is never evidence that Kalshi has no such market. For more wins, follow settled_wins.more, which carries ready-made search_settled_wins arguments.

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
limitNoMaximum items in each list (settled wins, roster markets, recently traded markets).
queryYesMarket title or keywords, e.g. "super bowl", "fed rate" or "bitcoin". Terms of 2+ characters, at most 8. All terms must match the title, outcome or tickers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Market title or keywords, e.g. \"super bowl\", \"fed rate\" or \"bitcoin\". Terms of 2+ characters, at most 8. Keyword matching ANDs them as substrings of the title, outcome and tickers (settled wins also match the event title); the full text is also fuzzy-matched to market series."New value: +"Market title or keywords, e.g. \"super bowl\", \"fed rate\" or \"bitcoin\". Terms of 2+ characters, at most 8. All terms must match the title, outcome or tickers."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well past the readOnlyHint/openWorldHint annotations: it discloses that results are gated by API key tier, that keyed calls consume 1 unit of daily quota, that unkeyed results are settled wins only and never a hit rate, and that `data.access` must be read and relayed. This is exactly the kind of behavioral context annotations cannot express.

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-loads the purpose and tier behavior, and nearly every sentence carries operational value (quota cost, data.access, empty-list caveat). It loses a little to the vague aside about 'the way the KalshiSpy app's search works' and the awkward schema-name sentence.

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

Completeness5/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 carries the full burden and does so: it names the return buckets (`settled_wins`, `open_markets`), the status field to inspect (`data.access`), the pagination handle (`settled_wins.more`), and the citation field (`kalshi_url`). An agent can call this and interpret the response correctly.

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 both `query` and `limit` are already documented in structured fields and the baseline of 3 applies. The description adds no syntax guidance beyond the schema, and its instruction to 'send the words under the argument name this tool's own schema gives' is meta rather than semantic.

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?

Opens with a specific verb and resource ('Find Kalshi markets by title or keywords') and immediately scopes the result set by API-key tier, so the agent knows this is a dual-mode search. It also points at the sibling 'search_settled_wins' for follow-up queries, making it distinguishable from the other search tool without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Call this first whenever the user names a market in words') plus the alternative path ('For more wins, follow `settled_wins.more`, which carries ready-made search_settled_wins arguments'). It also states the when-not caveat that an empty list is not evidence of absence, which prevents a common misinference.

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