Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kalshi_market_orderbook

Fetch a Kalshi market order book by ticker to view yes/no bid levels with price and size. Kalshi lists bids only, so ask levels are not included.

Instructions

Kalshi market orderbook. Returns the order book for one Kalshi market by ticker: bid levels for the yes side and the no side, each with price and size. Kalshi publishes bids only, so ask levels are not listed. The response also carries a raw_unit_hint for the price unit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ticker": "<ticker>"
    },
    "name": "kalshi_market_orderbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickerYesKalshi market ticker

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. 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 burden and does a good job disclosing a genuinely non-obvious trait: 'Kalshi publishes bids only, so ask levels are not listed.' It also sketches the return shape (yes/no bid levels with price and size, plus raw_unit_hint). It stops short of auth, rate-limit, or freshness details, but the bids-only disclosure is real value beyond structured fields.

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?

Four short sentences, front-loaded with the purpose and then the return shape and the bids-only caveat. Every sentence carries information; nothing is redundant.

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?

No output schema exists, and the description compensates by explaining the return contents (bid levels per side, price/size fields, raw_unit_hint). Missing only operational context like auth or freshness, so it is nearly complete for a simple single-param lookup.

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 description coverage is 100%, so the single ticker parameter is already documented in the schema. The description only adds that the ticker identifies 'one Kalshi market', which is marginal. Baseline 3 is appropriate when the schema does the heavy lifting.

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 the order book for one Kalshi market by ticker') and scopes it to a single market, which implicitly distinguishes it from the batched kalshi_markets_orderbooks sibling. An agent can identify what this tool fetches without opening the schema.

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 'for one Kalshi market by ticker' phrasing implies the single-market use case, but it never explicitly says when to prefer this over kalshi_markets_orderbooks or any other Kalshi endpoint. Usage is inferable rather than stated.

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