Skip to main content
Glama
pmxt-dev

pmxt-mcp

Official
by pmxt-dev

fetchMarket

Read-only

Search for a single prediction market by ID, slug, keyword, or other criteria across multiple exchanges.

Instructions

Fetch a single market by lookup parameters. Convenience wrapper around fetchMarkets() that returns a single result or throws MarketNotFound.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
exchangeYesThe prediction market exchange to target.
limitNoMaximum number of results to return
offsetNoPagination offset — number of results to skip
sortNoSort order for results
statusNoFilter by market status (default: 'active', 'inactive' and 'closed' are interchangeable)
searchInNoWhere to search (default: 'title')
queryNoFor keyword search
slugNoFor slug/ticker lookup
marketIdNoDirect lookup by market ID
outcomeIdNoReverse lookup -- find market containing this outcome
eventIdNoFind markets belonging to an event
pageNoFor pagination (used by Limitless)
similarityThresholdNoFor semantic search (used by Limitless)
verboseNoReturn full uncompacted response. Default false returns a compact, agent-friendly summary.
Behavior4/5

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

Annotations indicate readOnlyHint: true, and the description adds that it throws MarketNotFound on missing results. No contradictions, but no further behavioral details like rate limits.

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 with front-loaded verb and purpose. No wasted words.

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?

Given high schema coverage, the description is reasonably complete. However, for a complex tool with 14 parameters and no output schema, additional guidance on parameter priority would improve completeness.

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 description adds no extra meaning. Baseline 3 is appropriate; the description does not explain parameter precedence or overlap.

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 fetches a single market by lookup parameters, distinguishing it from fetchMarkets() as a convenience wrapper that returns a single result or throws MarketNotFound.

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 for single market lookup via convenience wrapper, but does not explicitly state when to avoid or list alternative tools beyond fetchMarkets().

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