Skip to main content
Glama
Polymarket MCP Server

Polymarket MCP Server

by yashhsm

get_leaderboard

Fetch Polymarket trader leaderboard rankings to compare profitable or high-volume traders, filtered by category, time period, username, or wallet address.

Instructions

Fetch Polymarket trader leaderboard rankings (most profitable / highest volume traders)

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

NameRequiredDescriptionDefault
userNoFilter by user address
limitNoNumber of results (1-50)
offsetNoPagination offset (0-1000)
orderByNoOrder by PNL or volume
categoryNoLeaderboard category
userNameNoFilter by username
timePeriodNoTime period for rankings

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden and it does not. It omits whether this is a read-only query, any auth or rate-limit expectations, and how pagination and default ordering behave; it also does not mention that defaults exist for period or category. Because the schema has 7 parameters but the description addresses none, the gaps are significant.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler. It is appropriately terse for a list query, though the parenthetical could have been spent on more useful behavioral detail.

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

Completeness2/5

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

With 7 optional parameters, three enums, and no output schema, the definition is underspecified: it never says what a ranking record contains, what the default timePeriod or category is, or how offset interacts with limit. For a leaderboard tool likely to be called without arguments, those defaults matter.

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 100%, with clear enum descriptions and limits on limit and offset, so parameters are already well documented. The description adds no semantics beyond "most profitable / highest volume," which loosely maps to the orderBy enum but gives no defaults or usage guidance. Baseline 3 applies when the schema already handles parameter meaning.

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 names a specific verb and resource ("Fetch Polymarket trader leaderboard rankings") and clarifies the two ranking dimensions in parentheses. No sibling tool in the list does leaderboard retrieval, so an agent can identify it immediately.

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?

The description gives no explicit when-to-use guidance, prerequisites, or alternatives to differentiate it from options such as get_user_activity or get_top_holders. It does not tell the agent when a leaderboard is the right call versus per-wallet or per-market tools.

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