Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

kalshi_market_history

Retrieve historical candlestick data for a Kalshi market by ticker to analyze price movements across a custom time range and interval.

Instructions

Kalshi market history. Returns candlesticks for one Kalshi market by ticker. series_ticker defaults to the ticker prefix before the last dash, start_ts to 7 days ago, end_ts to now and period_interval to 1440 minutes. include_latest_before_start adds the last candle before the start. Ranges are capped at 366 days.

Input Schema

NameRequiredDescriptionDefault
end_tsNoUnix end timestamp in seconds. Defaults to now.
tickerYesKalshi market ticker
start_tsNoUnix start timestamp in seconds. Defaults to 7 days ago.
series_tickerNoKalshi series ticker. Defaults to the market ticker prefix before the last dash.
period_intervalNoCandlestick interval in minutes. Default: 1440.
include_latest_before_startNoInclude the latest candle before start_ts when supported upstream.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.6/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 burden and does meaningful work: it discloses that ranges are capped at 366 days, gives every parameter's default, and explains include_latest_before_start's effect. It omits auth needs, rate limits, and return/candle format, keeping it out of 5 territory.

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

Conciseness5/5

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

Dense and front-loaded: purpose first, then defaults, then the edge-case flag and the range cap. Every sentence adds information with no waste.

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 read-only candlestick retrieval tool with 6 params and no output schema, the description covers defaults and the 366-day cap well. It doesn't describe the candle/return shape, which is the main remaining gap.

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 every parameter is already documented in the schema; the description's default explanations largely restate the schema descriptions. Baseline 3 is appropriate when the schema does the heavy lifting.

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+resource: 'Returns candlesticks for one Kalshi market by `ticker`. The singular 'one market' implicitly distinguishes it from the plural markets_history sibling, but no sibling is named explicitly, so it stops short of a 5.

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 explicit when-to-use, when-not, or alternative tool guidance. Given the many kalshi_* siblings (kalshi_market, kalshi_markets_history, kalshi_historical_market_history), the agent must infer which one to pick from the description alone.

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