Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kalshi_markets_orderbooks

Fetch order books for up to 25 Kalshi markets in one call by ticker; returns yes/no bid price and size levels in the requested order.

Instructions

Kalshi batch market orderbooks. Returns order books for up to 25 Kalshi markets in one call. tickers is required, as a comma-separated list or repeated values. Each book has the yes and no bid levels with price and size; ask levels are not listed. Books come back in the order requested.

Input Schema

NameRequiredDescriptionDefault
tickersYesComma-separated Kalshi market tickers. Repeated query values are also accepted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. Addedv1.1.0

TDQS

A4/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 behavioral burden and discloses key traits: a 25-market cap, returned fields ('yes' and 'no' bid levels with 'price' and 'size'), the absence of ask levels, and preserved request ordering. It does not cover auth or error behavior, but for a read-only market-data tool this is strong disclosure.

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?

Front-loaded with the tool's identity and purpose, then parameters, output shape, and ordering behavior. Each of the five short sentences adds actionable information with no waste.

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?

There is no output schema, and the description compensates by explaining the returned book structure and the batch limit. An agent can interpret results correctly, though error handling for oversized ticker lists is not addressed.

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. The description repeats that `tickers` is required and accepts comma-separated or repeated values, and adds the useful 'up to 25' cap, but adds no further format or validation semantics beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Returns order books' for 'Kalshi markets.' The 'batch' qualifier and 'up to 25 Kalshi markets in one call' scope clearly distinguish it from the single-market sibling kalshi_market_orderbook.

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?

The batch context ('up to 25 ... in one call') implies when to use this tool, but no alternative such as kalshi_market_orderbook is named, and there are no explicit when-not conditions.

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