Fetch media, market metadata, settlement sources, and optional competition context for a specific Kalshi event using its ticker.
Kalshi event metadata. Returns media, market metadata, settlement sources, and optional competition context for one Kalshi event 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 bears full burden. It notes 'credential-free' (no auth) and 'public data', but lacks disclosure of error handling, rate limits, or data freshness.
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?
The description is a single concise sentence that lists returned data. It is efficient but could be slightly more structured (e.g., bullet points) to improve scanning.
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?
Given the tool has one parameter, the description adequately explains what is returned (media, market metadata, settlement sources, optional competition context). Lacks output schema but sufficient for a simple metadata lookup.
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 description coverage is 100% with the parameter description 'Kalshi event ticker'. The tool description adds no additional meaning or format details beyond this, so baseline 3 applies.
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 the tool returns specific metadata (media, market metadata, settlement sources, optional competition context) for one Kalshi event from public data, distinguishing it from siblings like kalshi_event or kalshi_markets.
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 guidance on when to use this tool versus alternatives such as kalshi_event or kalshi_market. The description implies it's for detailed metadata but lacks explicit when/when-not or alternative references.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.