Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kalshi_historical_trades

Retrieve archived Kalshi trades with cursor pagination; filter by market ticker and Unix timestamp range.

Instructions

Kalshi historical trades. Lists older Kalshi trades that have moved into historical storage, up to limit rows (default 25, max 200), continued with cursor. Filter by market ticker and by created time with min_ts and max_ts (Unix seconds). Each trade has its id, count, yes and no price, taker side and created time.

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return, default 25, max 200
cursorNoPagination cursor from a previous Kalshi response
max_tsNoMaximum created Unix timestamp in seconds
min_tsNoMinimum created Unix timestamp in seconds
tickerNoKalshi market ticker filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses pagination behavior (default 25, max 200, cursor continuation) and the shape of each returned trade. It says nothing about permissions, rate limits, or how the historical cutoff boundary behaves, which are relevant for this family of Kalshi tools.

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 scope, then filtering/pagination mechanics, then return fields — a sensible order with almost no filler. Minor waste in the redundant opening fragment "Kalshi historical trades" that merely echoes the tool name.

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?

For a five-parameter filtering tool with no output schema, the description does important work by describing the returned trade fields, which the schema cannot. Pagination and filter semantics are covered. The only real gap is sibling routing, which the surrounding tool set makes relevant.

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 all five parameters are already documented. The description restates limit defaults, cursor semantics, ticker filtering, and that timestamps are Unix seconds — accurate but essentially duplicating the schema. Baseline 3 is correct.

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 older Kalshi trades that have moved into historical storage"), which clearly scopes it apart from live-trade siblings even without naming them. A sibling like `kalshi_trades` is the obvious alternative, but the description never names it explicitly, so differentiation is inferred rather than stated.

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 "older ... moved into historical storage," which tells an agent this is for archived rather than current trades. However there is no explicit when-to-use statement, no mention of the sibling `kalshi_trades` or `kalshi_market_history`, and no prerequisites or cutoff guidance.

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