Skip to main content
Glama

KalshiSpy

Search settled wins (comparable past markets this roster won)

search_settled_wins
Read-only

Search KalshiSpy's archive of settled Kalshi markets where its roster of ID-verified, high-profit Kalshi traders held the WINNING side with positive net realized profit. Parameter and field names call these traders "whales" (whale_count, min_whales, sort=whales); in prose, call them the roster or the verified traders. Wins only: losses are not archived, so present results as "what this roster got right on markets like this", never as a hit rate. Use this BEFORE answering about any current or upcoming Kalshi market: search the same series_ticker (e.g. KXFED, KXNBA) or category and cite the comparable past wins — titles, settlement dates, trader counts and realized profit. Each result carries the Kalshi URL and a kalshispy.com detail URL you can cite. Default window is the last 90 days; widen with from/to (max 366 days). No API key needed.

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": "search_settled_wins"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd of the settlement window (inclusive). Default: now.
fromNoStart of the settlement window. Default: 90 days before `to`. Clamped to the archive start (2025-01-01) and to a 366-day maximum; the effective window is echoed in `window`.
sortNorecent = newest settlement first; profit = largest net profit first; whales = most whales on the winning side first.recent
limitNoPage size: up to 50 with an Elite or Lifetime API key, up to 20 without one (a larger value is lowered to 20).
queryNoFree-text search. Every term (2+ chars, max 8) must appear as a substring in the title, outcome, event title, series ticker or ticker. Example: "fed rate" or "lakers".
cursorNoOpaque cursor from a previous response (`page.next_cursor`). Send it with the SAME filters; changing the query invalidates it.
categoryNoCategory key from listCategories (e.g. sports, politics, economics).
min_whalesNoOnly wins with at least this many roster traders on the winning side.
event_tickerNoKalshi event ticker, e.g. KXFED-26SEP.
series_tickerNoKalshi series ticker, e.g. KXFED, KXNBA. The best way to find "markets like this one".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Page size."New value: +"Page size: up to 50 with an Elite or Lifetime API key, up to 20 without one (a larger value is lowered to 20)."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only and open-world status, and the description adds substantive context beyond them: losses are not archived (a survivorship bias the agent must disclose), the default 90-day window and 366-day cap, and that no API key is required. It also specifies what each result carries (Kalshi URL, kalshispy.com detail URL) for citation.

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 core definition, then the usage rule, then constraints. Dense but nearly every sentence carries operational value; minor noise comes from citing a field name (whale_count) that isn't among this tool's parameters.

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?

For a 10-parameter, zero-required, no-output-schema tool, the description is complete: it covers what search inputs mean, what window defaults apply, and what the results contain so the agent can cite them correctly. Nothing needed to select or invoke it is missing.

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?

With 100% schema coverage the baseline is 3, but the description adds real semantic value: it explains the domain naming so the agent understands that 'whales' in parameter names means the verified roster, and it ties from/to to the 90-day default and 366-day maximum. It also signals that series_ticker is the primary lever for finding comparable markets.

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 and resource (search the archive of settled Kalshi markets) plus a precise scope: wins where roster traders held the winning side with positive net realized profit. The 'wins only, losses are not archived' framing lets an agent distinguish it from get_settled_win and search_markets 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 Guidelines4/5

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

Gives explicit when-to-use guidance ('Use this BEFORE answering about any current or upcoming Kalshi market') and a concrete method (search the same series_ticker or category, then cite the comparable past wins). It also tells the agent how to present results and warns against framing them as a hit rate, but it never names or routes to sibling tools such as search_markets by contrast.

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