Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kalshi_event

Fetch details for a Kalshi event and its markets using an event ticker. Includes prices, volume, status, and rules; returns not-found for unknown tickers.

Instructions

Kalshi event detail. Returns one Kalshi event by event_ticker (such as KXELONMARS-99) together with its markets. The event has its series ticker, title, subtitle, category, strike period and mutually-exclusive flag; each market has prices, bid and ask, volume, open interest, status and rules. An unknown ticker returns a not-found error.

Input Schema

NameRequiredDescriptionDefault
event_tickerYesKalshi event ticker

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.9/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 disclosure burden and does a solid job: it spells out the returned fields for both the event and each nested market, and it discloses error behavior ('An unknown ticker returns a not-found error'). It omits auth requirements and rate limits, which keeps it short of a 5.

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?

Three tightly packed sentences, front-loaded with the core purpose, followed by return contents and then the error case. Every sentence adds information an agent cannot get from the schema or (absent) annotations.

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?

With no output schema, the description steps in to describe the return shape (event fields plus nested market fields) and error behavior, which is exactly what an agent needs for a single-record lookup. Only the absence of auth/permission notes keeps it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single parameter, so the baseline is 3, but the description adds real value by giving a concrete example ticker format (`KXELONMARS-99`) that the terse schema description ('Kalshi event ticker') does not provide.

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 Kalshi event by event_ticker along with its markets, and enumerates the event- and market-level fields returned. It implicitly distinguishes the singular detail lookup from the plural list tool (kalshi_events), but never names a sibling, leaving potential overlap with kalshi_event_metadata or kalshi_event_history unaddressed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent infers it should call this when it already holds an event_ticker and wants full detail. There is no explicit when-to-use statement, no when-not to use this, and no routing to the nearest alternatives such as kalshi_event_metadata or kalshi_events.

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