Skip to main content
Glama
guangxiangdebizi

Polymarket MCP Server

get_markets

Retrieve Polymarket prediction markets with filters and pagination to access prices, volume, liquidity, and metadata.

Instructions

Retrieve Polymarket prediction markets with filtering and pagination options. Get market data including prices, volume, liquidity, and metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of markets to return (default: 20, max: 100)
orderNoField to sort by (volume, liquidity, start_date, end_date)
activeNoFilter by active status - true for active markets only
closedNoFilter by closed status - false to exclude closed markets
offsetNoNumber of markets to skip for pagination (default: 0)
searchNoSearch term to filter markets by title or description
tag_idNoFilter markets by specific tag/category ID
archivedNoFilter by archived status - false to exclude archived markets
ascendingNoSort direction - true for ascending, false for descending (default: false)
volume_minNoMinimum volume threshold in USDC
liquidity_minNoMinimum liquidity threshold in USDC
Behavior3/5

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

The description indicates a read operation without side effects. Since no annotations are provided, it carries full burden but only states that it retrieves data; no mention of rate limits, auth, or error behavior. Adequate for a simple read tool.

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 with no filler. The first sentence states the main purpose and features, making it immediately useful.

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?

The description mentions return fields (prices, volume, liquidity, metadata) but not the return type (list). Pagination behavior is implicit via parameters. Given no output schema and 11 optional parameters, the description is adequate but lacks explicit detail on output structure.

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?

Input schema covers all parameters with descriptions (100% coverage). The description adds high-level context ('filtering and pagination') but does not enhance individual parameter meaning 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 the verb 'Retrieve' and the resource 'Polymarket prediction markets', with specific mention of filtering and pagination. It distinguishes from siblings like get_events and get_market_prices by focusing on markets.

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?

No guidance on when to use this tool vs alternatives. It does not specify exclusions or scenarios where sibling tools like get_events or get_market_prices would be more appropriate.

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/guangxiangdebizi/PolyMarket-MCP'

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