polymarket-mcp-server

Overview Schema Source Related Servers Discussions Admin

Get Polymarket trader leaderboard

polymarket_get_leaderboard

Read-onlyIdempotent

Rank Polymarket traders globally by realized profit or traded volume over a chosen time window and category to identify top-performing wallets.

Instructions

Get the trader LEADERBOARD — top wallets ranked by realized profit (PnL) or traded volume over a time window.

Args:

order_by ('PNL' | 'VOL'): rank by profit or volume (default 'PNL').
time_period ('DAY' | 'WEEK' | 'MONTH' | 'ALL'): window (default 'MONTH').
category (string, optional): e.g. OVERALL, POLITICS, SPORTS, CRYPTO, CULTURE, ECONOMICS, TECH, FINANCE.
limit (number): top N traders, 1-50 (default 10).
response_format ('markdown' | 'json'): default 'markdown'.

Returns: { orderBy, timePeriod, count, entries:[{ rank, wallet, name, pnl, volume }] }. This is a global ranking (unlike polymarket_get_market_holders, which is per-market).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Top N traders (1-50, default 10).
`category`	No	Optional category, e.g. OVERALL, POLITICS, SPORTS, CRYPTO, CULTURE, ECONOMICS, TECH, FINANCE.
`order_by`	No	Rank by profit ('PNL') or volume ('VOL'). Default 'PNL'.	PNL
`time_period`	No	Window: DAY, WEEK, MONTH or ALL (default MONTH).	MONTH
`response_format`	No	Output format: 'markdown' (concise, human-readable; default) or 'json' (full structured data).	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`entries`	Yes
`orderBy`	Yes
`timePeriod`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 28, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the burden is lighter. The description adds the ranking semantics (realized PnL vs. volume) and the global-vs-market scoping behavior, though it says nothing about rate limits, auth, or pagination.

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?

Front-loaded purpose sentence, then a clean Args block with defaults and a Returns line. No wasted prose; each line earns its place.

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?

An output schema exists, yet the description still summarizes the return shape for convenience. Combined with full parameter documentation and annotation-backed safety, an agent has everything needed to invoke it correctly.

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 every parameter is already documented in the schema. The description largely restates the same defaults, enums, and category examples, adding little meaning beyond the structured fields. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Get the trader LEADERBOARD') plus the exact ranking basis (realized profit or traded volume) and time window. It explicitly differentiates itself from the sibling polymarket_get_market_holders by noting this is a global ranking versus a per-market one.

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

Usage Guidelines5/5

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

Clearly routes the agent: use this for global wallet rankings, use polymarket_get_market_holders for per-market holders. The condition that selects this tool (global vs. per-market) is stated rather than left to inference.

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