Returns Kalshi's cutoff timestamps for historical market, order, and trade data migration. Use to identify when data becomes historical.
Kalshi historical data cutoff. Returns the cutoff timestamps Kalshi uses for historical market, order, and trade data migration.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses that the tool returns timestamps, but does not mention any behavioral aspects such as side effects, rate limits, or authentication needs. The tool appears read-only, but this is not explicitly stated.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Extremely concise: two sentences with no redundant words. The first sentence clearly states the tool's purpose, and the second elaborates on the output. Highly front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple metadata tool with no parameters and no output schema, the description provides sufficient context. It explains exactly what is returned and for what purpose, making it complete for the agent to understand its usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has no parameters, and schema coverage is 100% (empty schema). The description adds meaning by explaining what the output represents, which is above the baseline of 4 for zero parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it returns cutoff timestamps for historical data migration. It specifies the resource (cutoff timestamps) and the action (returns), distinguishing it from siblings like kalshi_historical_market which provide actual market data.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives. The description implies it is a prerequisite for historical data queries, but does not state when or when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.