Fetch a Kalshi event and its normalized markets from public market-data JSON using an event ticker, returning one clean event row for analysis.
Kalshi event detail. Returns one normalized Kalshi event row and its normalized markets from credential-free public market-data JSON.
| Name | Required | Description | Default |
|---|---|---|---|
| event_ticker | Yes | Kalshi event ticker |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Mentions 'credential-free public market-data JSON' which implies read-only, but lacks details on rate limits, data freshness, or side effects. More context needed.
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?
Single sentence, no fluff, efficiently conveys purpose. Slightly more detail could be added without losing conciseness.
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?
No output schema or annotations. Description defines return content (normalized event row and markets) and credential-free access, but lacks format details or example. Adequate for a simple single-parameter tool.
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?
Schema coverage is 100% and the schema already describes 'event_ticker' as 'Kalshi event ticker'. Description does not add additional meaning beyond what the schema provides.
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 a Kalshi event detail with normalized event row and markets. It distinguishes from siblings like kalshi_events (plural list) and kalshi_event_metadata (metadata only), but could explicitly state 'use for a single event by ticker'.
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?
Implied usage for getting event details, but no explicit when-to-use or alternatives guidance. Sibling tools like kalshi_events serve different purposes, but description doesn't clarify.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.