mcp-server-polymarket

Overview Schema Source Related Servers Discussions Admin

Get the trader leaderboard

get_leaderboard

Read-onlyIdempotent

Rank Polymarket traders by realized PnL or volume across day, week, month, or all-time windows, or retrieve a single wallet's leaderboard standing.

Instructions

Top traders by realised PnL or volume over a window, or one wallet's standing.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_leaderboard"
  }
}

Input Schema

Name	Required	Description	Default
`user`	No	One wallet's ranks instead of the board.
`limit`	No	Rows per page.
`cursor`	No	next_cursor from the previous page. Empty starts at the top.
`window`	No		day
`sort_by`	No		PNL
`category`	No	overall, a market category such as sports, or combos.	overall

Output Schema

Name	Required	Description	Default
`note`	No
`count`	No
`items`	No
`has_more`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds the meaningful behavioural detail that rankings are based on realised PnL (not unrealised) and that results are windowed, but it says nothing about pagination behaviour, default ordering, or how ties/empty boards are handled.

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?

A single front-loaded sentence covering the board mode, the two metrics, the time window, and the wallet-scoped variant, with no filler. Nothing can be trimmed without losing 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?

An output schema exists, so return values need not be explained, and the schema documents limit, cursor, and category. For a 6-parameter tool with two modes the definition is adequate, but it leaves the interaction between category and board scope, and any pagination nuance, to the schema alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the two undocumented enum parameters are exactly the ones the description rescues: 'realised PnL or volume' explains sort_by's PNL/VOLUME values, and 'over a window' scopes the unnamed window enum. The 'one wallet's standing' phrasing also clarifies the user parameter's mode-switching role beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (leaderboard), the ranking metrics ('realised PnL or volume'), and the time scope ('over a window'), plus the alternate single-wallet mode. That is enough to distinguish it from nearby tools like get_user_pnl or get_profile, though it never names them explicitly.

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

Usage Guidelines3/5

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

Implicit guidance comes from the 'or one wallet's standing' clause, which tells the agent that supplying a wallet switches from the board to a single standing. There is no explicit when-to-use versus sibling tools such as get_user_pnl, and no stated exclusions or prerequisites.

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

Deploy Server