Skip to main content
Glama
predmarket-mcp

predmarket-mcp

get_orderbook

Read-only

Retrieve a prediction market's YES-side order book with bids, asks, and spread; Kalshi NO bids are converted to YES asks for venue-neutral quoting.

Instructions

YES-side order book: bids best-first, asks best-first, plus the spread.

Kalshi NO bids are converted to YES asks (a NO bid at p equals a YES ask at 1 - p).

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": {
      "venue": "<venue>",
      "market_id": "<market_id>"
    },
    "name": "get_orderbook"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNo
venueYes
market_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful non-obvious behavior: Kalshi NO bids are normalized into YES asks using 1 - p, which changes how an agent must read results. It says nothing about depth truncation or error behavior.

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?

Two tight sentences with the primary description front-loaded and the price-conversion caveat second. Nothing is padded, and the caveat earns its place because it changes interpretation of the output.

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?

An output schema exists, so return-value mechanics need not be re-explained, and the description still complements it with side-normalization and ordering semantics. The main remaining gap is the undocumented depth and venue parameters for a two-venue tool.

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 0% across three parameters, so the description would ideally explain venue, market_id, and depth. It adds nothing about any of them; the best-first wording only loosely hints at ordering relative to depth. The conversion rule is the only semantic content.

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 the specific resource (YES-side order book) and its shape: bids best-first, asks best-first, plus the spread. An agent can distinguish it from get_recent_trades or get_price_history by resource alone, though the retrieval verb is only implicit.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no named alternative (e.g. versus get_market or compare_venues). Usage is only inferable from the resource name, so the description does not route an agent between siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.