Skip to main content
Glama

Fetches top-ranked traders on Polymarket ranked by overall

pm_leaderboard
Read-only

Fetches top-ranked traders on Polymarket ranked by overall profit or trading volume across customizable time windows (day, week, month, all). Includes rank, wallet address, username/pseudonym if public, profit PnL, and total trading volume. Information only, not financial advice. Related tools on this server, for a different need: pm_event when you need to fetch details for a single Polymarket event by slug; pm_history when you need to fetch historical price points for a Polymarket outcome. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "window": "<window>"
    },
    "name": "pm_leaderboard"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of top traders to return (max 100)
sortByNoMetric to rank by: profit (default) or volume
windowYesTime window: day, week, month, or all

Output Schema

NameRequiredDescriptionDefault
countNo
sortByNo
sourceNo
windowNo
checkedAtNo
disclaimerNo
leaderboardNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real context the annotations do not: the exact fields returned, a cost model ($0.003 per successful call via x402, failures uncharged), and a not-financial-advice disclaimer. However, the returned-field list duplicates the output schema, and nothing is disclosed about rate limits or data freshness.

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?

Front-loaded with purpose before the sibling routing, then fields, then commercial terms – a sensible order. The 'Information only, not financial advice' line and the payment-rail enumeration are boilerplate-heavy, but each still carries usable information rather than pure repetition.

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?

With an output schema present, the description need not explain return values, and it covers cost, ranking dimensions, and time windows adequately for a 3-parameter read-only tool. The main gap is freshness/caching behavior, which matters for a live leaderboard.

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%, so all three parameters are already documented, and the description only restates them ('profit or trading volume', 'day, week, month, all') without adding syntax, defaults beyond profit, or limits beyond what 'max 100' already says. Baseline 3 applies.

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 ('Fetches top-ranked traders on Polymarket') plus the ranking dimension ('overall profit or trading volume') and the scoping axis (time windows), which lets an agent separate it from pm_event, pm_history and the other pm_* siblings without opening a schema.

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?

Explicitly routes to alternatives with conditions: pm_event for a single event by slug, pm_history for historical price points. That is genuine when-to-use-else guidance, but it does not state exclusions for close cousins like pm_wallet or pm_activity, which are the likelier confusion points for a trader-ranking tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources