Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kalshi_historical_market

Retrieve a settled Kalshi market by ticker to get result, prices, volume, liquidity, and rules for historical analysis.

Instructions

Kalshi historical market detail. Returns one settled Kalshi market from historical storage by ticker. The response has the title, subtitle, event ticker, status, result, open, close and expiration times, last and previous price, yes and no bid and ask, volume, open interest, liquidity and primary rules text. Invalid tickers are rejected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesKalshi historical market ticker

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It usefully enumerates the returned fields and states that invalid tickers are rejected, which is genuine behavioral context. It does not, however, cover permission requirements, rate limits, or whether the tool is a read-only operation beyond the implicit 'returns'.

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 the core purpose in the first sentence, followed by response contents and error behavior. The field enumeration is long but each item earns its place because there is no output schema to carry that information. No filler sentences.

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 single-parameter lookup with no output schema, the explicit listing of returned fields plus the invalid-ticker behavior makes the definition largely self-sufficient. The only material gap is the absence of any routing guidance relative to the live-market and list siblings.

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 the single ticker parameter; that sets the baseline at 3. The description reinforces that the ticker identifies a settled historical market, but adds no format, example, or lookup guidance beyond what the schema provides.

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 one settled Kalshi market from historical storage by ticker'. The words 'settled' and 'historical storage' implicitly contrast with the live kalshi_market sibling, so an agent can broadly infer the distinction. However, it never explicitly names kalshi_market or kalshi_historical_markets, so the differentiation relies on inference rather than being stated.

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?

There is no explicit when-to-use guidance and no mention of alternatives. The description never tells the agent when to prefer the historical endpoint over the live kalshi_market or the list-level kalshi_historical_markets. Usage is only implied by the required ticker parameter.

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