Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kalshi_events

List Kalshi events by series ticker, category, status, close time, or update time; paginate results and optionally include nested markets.

Instructions

Kalshi events. Lists Kalshi events, up to limit rows (default 25, max 200), continued with cursor. Filter by series_ticker, category, status (open, closed or settled), min_close_ts and min_updated_ts. with_nested_markets adds each event's markets. Each event has its ticker, title, category and strike period. A cursor is returned when more rows exist.

Input 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

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does so reasonably well: it discloses the default (25) and max (200) page size, the cursor pagination contract ('a cursor is returned when more rows exist'), and that nested markets are opt-in. It does not cover auth/permission needs or rate limits, so it stops short of full transparency.

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-loaded with purpose, then pagination, then filters, then return shape — a sensible ordering. Dense but every sentence carries information; only the redundant opening fragment 'Kalshi events.' wastes space.

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

Completeness4/5

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

With no output schema and no annotations, the description compensates by describing the return fields ('ticker, title, category and strike period') and pagination behavior. The gap is minor: with_milestones is unmentioned and no guidance on auth or error behavior is given, but for a read-only list endpoint the essentials are present.

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 defines all nine parameters and a baseline of 3 applies. The description restates eight of them (limit, cursor, status, category, min_close_ts, series_ticker, min_updated_ts, with_nested_markets) but adds no syntax or format detail beyond the schema, and omits with_milestones entirely.

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 ('Lists Kalshi events') and adds scope details (filters available, pagination). It is clearly distinguishable from single-entity siblings like kalshi_event or kalshi_markets, though it never names them 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?

Usage is implied by the enumerated filters ('Filter by series_ticker, category, status...'), which tells an agent when the tool fits. However, there is no explicit when-to-use versus when-to-use-something-else guidance, and no mention of the sibling tools (kalshi_event, kalshi_series) an agent might otherwise pick.

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