Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kalshi_events

Fetch and filter Kalshi event market data from public JSON, using status, category, series, and pagination options. Get normalized rows for analysis or integration without credentials.

Instructions

Kalshi events. Returns normalized Kalshi event rows from credential-free public market-data JSON.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows to return, default 25, max 200
cursorNoPagination cursor from a previous Kalshi response
statusNoEvent status filter
categoryNoKalshi category filter
min_close_tsNoMinimum event close Unix timestamp in seconds
series_tickerNoKalshi series ticker filter
min_updated_tsNoMinimum event update Unix timestamp in seconds
with_milestonesNoInclude event milestones when supported upstream
with_nested_marketsNoInclude nested market rows when supported upstream

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / status / enum
      Added value: +[
+  "open",
+  "closed",
+  "settled"
+]
  2. Addedv1.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It does disclose that the data is credential-free and public, and that rows are normalized, which hints at a read operation. However, it omits pagination behavior (cursor is a parameter), rate limits, or any side effects. For a listing tool with no annotation coverage, this is insufficient disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but the first sentence 'Kalshi events.' is essentially a tautology of the tool name and adds little value. The second sentence provides useful context but is minimal. It is not front-loaded with the most actionable information, and the redundant first sentence reduces its efficiency.

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?

Given 9 optional parameters, no output schema, and no annotations, the description is far too sparse. It does not explain how pagination works, what 'normalized' means in practice, or how filters like status, category, and timestamps behave. An agent would need to infer most usage details from the schema alone, which is risky.

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 the baseline is 3. The description adds no extra meaning to the nine parameters—it does not explain cursor usage, filter semantics, or the 'with_milestones'/'with_nested_markets' flags beyond what the schema already states.

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?

The description states the verb 'returns' and the resource 'Kalshi events', and clarifies the output as normalized rows from public JSON. However, it does not distinguish itself from sibling tools like kalshi_event or kalshi_markets, which likely serve similar listing or detail purposes.

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 guidance is given on when to use this tool versus the many related Kalshi tools (kalshi_event, kalshi_markets, kalshi_historical_markets, etc.). The description does not mention alternatives, exclusions, or preferred contexts.

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