Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kalshi_market

Fetch Kalshi market details by ticker, including status, prices, bids, asks, volume, liquidity, and rules; unknown tickers return a not-found error.

Instructions

Kalshi market detail. Returns one Kalshi market by ticker (such as KXELONMARS-99). 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, 24-hour volume, open interest, liquidity and rules text. An unknown ticker returns a not-found error.

Input Schema

NameRequiredDescriptionDefault
tickerYesKalshi market ticker

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.8/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 burden and does reasonably well: it describes the returned fields (prices, bids/asks, volumes, open interest, liquidity, rules) and discloses the error behavior ('an unknown ticker returns a not-found error'). It doesn't explicitly restate read-only/idempotency, but for a read-only detail lookup this is genuinely informative.

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-loads the verb and resource in the first sentence, then uses the remaining space for the field enumeration, which is justified given there's no output schema. Slightly dense, but every sentence carries information an agent can use.

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?

Because no output schema exists, the description must describe return values — and it does, enumerating the market fields plus the error case. For a single-parameter retrieval tool this is complete, with the only gap being cross-references to sibling tools for the same resource.

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%, so the baseline is 3, but the description goes beyond the schema's bare 'Kalshi market ticker' by supplying a concrete example format (`KXELONMARS-99`), which helps an agent construct a valid value. That added meaning justifies exceeding the baseline.

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 market by ticker', which cleanly separates it from list-shaped siblings like kalshi_markets. It also names the return entity and field set, so an agent knows the shape. It stops short of explicitly contrasting with kalshi_market_history or kalshi_market_orderbook, so it isn't a full 5.

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 by 'one Kalshi market by ticker' — the singular framing hints this is a single-item lookup, but there is no explicit when-to-use or when-to-prefer-an-alternative guidance against kalshi_markets, kalshi_market_history, or kalshi_market_orderbook. Functional but leaves routing inference to the agent.

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