pmxt-mcp

Official

Overview Schema Source Related Servers Discussions Admin

fetchOrderBooks

Read-only

Fetch order books for multiple outcomes across prediction markets in one request, supporting exchanges like Polymarket and Kalshi.

Instructions

Batch variant of {@link fetchOrderBook}. Fetches order books for multiple outcomes in a single request where the exchange supports it.

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": {
      "exchange": "<exchange>",
      "outcomeIds": "<outcomeIds>"
    },
    "name": "fetchOrderBooks"
  }
}

Input Schema

Name	Required	Description
`exchange`	Yes	The prediction market exchange to target.
`outcomeIds`	Yes
`verbose`	No	Return full uncompacted response. Default false returns a compact, agent-friendly summary.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.46.14May 27, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already provide readOnlyHint=true, consistent with the description. The description adds minimal extra behavioral context, such as the batch aspect, but lacks details on error handling or exchange-specific behavior.

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 concise sentences, front-loaded with the key purpose and condition. No redundant information.

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?

For a simple 3-parameter read-only tool, the description covers the core purpose and key condition. Missing details like response format, but annotations suffice for safety.

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 67% (outcomeIds lacks description). The description mentions 'multiple outcomes', hinting at outcomeIds, but does not specify format or constraints 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?

The description clearly states it is a batch variant of fetchOrderBook, fetching order books for multiple outcomes in a single request. This distinguishes it from the sibling fetchOrderBook.

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 implies usage when multiple outcomes are needed and when the exchange supports batching. However, it does not explicitly state when not to use it or alternatives, but the sibling context provides differentiation.

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