pmxt-mcp

Official

Overview Schema Source Related Servers Discussions Admin

fetchMarketsPaginated

Read-only

Fetch prediction markets from supported exchanges using cursor-based pagination. First request caches all markets; subsequent calls use the cached snapshot until expiration.

Instructions

Fetch markets with cursor-based pagination backed by a stable in-memory snapshot. On the first call (or when no cursor is supplied), fetches all markets once and caches them. Subsequent calls with a cursor returned from a previous call slice directly from the cached snapshot — no additional API calls are made. The snapshot is invalidated after snapshotTTL ms (configured via ExchangeOptions in the constructor). A request using a cursor from an expired snapshot throws 'Cursor has expired'.

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>"
    },
    "name": "fetchMarketsPaginated"
  }
}

Input Schema

Name	Required	Description
`exchange`	Yes	The prediction market exchange to target.
`limit`	No
`cursor`	No
`filter`	No
`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.3/5.0

Behavior5/5

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

Goes beyond readOnlyHint annotation by detailing caching, snapshot invalidation after TTL, and the 'Cursor has expired' error. Provides full behavioral context.

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?

Single paragraph, front-loaded with purpose, each sentence adds value. No extraneous content.

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

Completeness3/5

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

Covers pagination behavior well but lacks parameter details and return value description. With no output schema, more clarity on response format would help.

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 only 40% (exchange and verbose have descriptions). Description clarifies cursor's role and expiration but does not explain limit, filter, or cursor format. Partial compensation.

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?

Description clearly states the verb (fetch), resource (markets), and pagination mode (cursor-based). It distinguishes from likely sibling `fetchMarkets` which is non-paginated.

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?

Describes when to use (first call without cursor triggers fetch, subsequent calls use cursor) and warns about expiration. Lacks explicit mention of alternatives, but context is clear.

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