Skip to main content
Glama
pmxt-dev

pmxt-mcp

Official
by pmxt-dev

fetchOrderBook

Read-only

Retrieve live or historical order book snapshots for any prediction market outcome, with support for range queries and compact summaries.

Instructions

Fetch the order book (bids/asks) for a specific outcome. Supports live and historical queries. For historical data, pass since to get a single snapshot, or since + until to get an array of fully reconstructed L2 books from the archive. Range queries return up to limit snapshots (default 100, max 1000).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
exchangeYesThe prediction market exchange to target.
outcomeIdYes
limitNo
sideNoOutcome side: 'yes' or 'no'. Required for exchanges like Limitless where the API returns a single orderbook per market.
outcomeNoOutcome alias: 'yes' or 'no', or an outcome token ID. When set, the first argument is treated as a market ID and this value selects which outcome's order book to fetch. Accepts the literal strings 'yes'/'no' (resolved via a market lookup) or a raw outcome token ID.
sinceNoUnix timestamp (ms) — fetch a historical snapshot at or before this time, or the start of a range when combined with `until` (hosted API only).
untilNoUnix timestamp (ms) — end of a historical range. When combined with `since`, returns an array of reconstructed L2 OrderBook snapshots between `since` and `until` (hosted API only).
verboseNoReturn full uncompacted response. Default false returns a compact, agent-friendly summary.
Behavior5/5

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

The description discloses behavioral traits beyond annotations, such as support for live and historical queries, snapshot vs range behavior, and limit constraints. No contradiction with readOnlyHint.

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?

Two sentences efficiently convey the main purpose and key parameter behaviors. Front-loaded with the core function, every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description explains return types (snapshot or array) and mentions compact vs verbose responses. It sufficiently covers what to expect for a fetch tool.

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?

The description adds semantics for parameters like 'since', 'until', 'limit', and 'verbose', explaining their roles in historical queries. With 75% schema coverage, this exceeds the baseline of 3.

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?

The description clearly states the tool fetches the order book for a specific outcome, distinguishing between live and historical queries. It is specific and differentiated from sibling tools like 'fetchOrderBooks'.

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

Usage Guidelines4/5

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

The description explains when to use historical vs live queries by detailing the 'since' and 'until' parameters. It does not explicitly contrast with sibling tools but implies context through parameter explanations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pmxt-dev/pmxt-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server