Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kalshi_historical_markets

Retrieve settled Kalshi historical market rows by ticker, event, or series, with pagination and filtering for research and analysis.

Instructions

Kalshi historical markets. Returns settled Kalshi historical market rows. tickers, event_ticker, and series_ticker are mutually exclusive. The mve_filter enum accepts exclude.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows to return, default 25, max 1000
cursorNoPagination cursor from a previous Kalshi response
tickersNoComma-separated Kalshi market tickers. Mutually exclusive with event_ticker and series_ticker.
mve_filterNoMultivariate event filter
event_tickerNoKalshi event ticker filter. Mutually exclusive with tickers and series_ticker.
series_tickerNoKalshi series ticker filter. Mutually exclusive with tickers and event_ticker.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / mve_filter / enum
      Added value: +[
+  "exclude"
+]
  2. Addedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it only says the tool returns settled rows. It does not disclose pagination behavior, auth/rate-limit requirements, result ordering, or how the historical cutoff applies.

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?

Four short clauses, front-loaded with the resource and followed by the key constraints. No wasted words, though the constraint sentences could be tied more directly to usage.

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

Completeness2/5

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

For a 6-parameter, no-annotation, no-output-schema tool, the description is thin: it omits return shape, pagination via cursor, and the practical effect of the historical cutoff. An agent can call it but cannot predict what it gets back or when it is the wrong choice.

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 description coverage is 100%, so the schema already documents every parameter including the mutual-exclusivity notes and the mve_filter enum. The description's restatement of those facts adds no meaning beyond the schema, so the baseline 3 applies.

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 ('Returns settled Kalshi historical market rows'), and 'settled'/'historical' implicitly distinguishes it from active-market siblings like kalshi_markets. However, it never names the closest siblings (kalshi_historical_market singular, kalshi_markets), so an agent must infer the boundary.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given. It notes that three filter params are mutually exclusive, but that is a parameter constraint, not a routing rule telling the agent when to pick this tool over kalshi_markets or kalshi_historical_market.

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

Deploy Server

Other Tools