graph-polymarket-mcp

get_top_traders

Identify leading Polymarket traders by realized P&L, win rate, or volume. Use minimum trade filters to exclude inactive accounts.

Instructions

Get the top Polymarket traders ranked by realized P&L, win rate, or volume from the Beefy P&L subgraph.

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_top_traders"
  }
}

Input Schema

Name	Required	Description	Default
`first`	No	Number of traders to return (1-100)
`orderBy`	No	Metric to rank traders by	totalRealizedPnl
`minTrades`	No	Minimum number of trades to filter out inactive accounts

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.0.0May 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are present, so the description carries the full burden. It discloses the ranking criteria and data source, implying a read operation. However, it does not specify sort order (ascending/descending), pagination behavior, or how the 'first' and 'minTrades' parameters affect results beyond their schema descriptions.

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?

The description is a single, focused sentence with no redundant content. It front-loads the core purpose and names the data source, achieving excellent conciseness.

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 tool is straightforward and its parameters are well-documented, but the lack of an output schema means the return format is undisclosed. It also does not mention sort direction or offer any comparison to sibling tools, leaving some context gaps for an agent.

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% with each parameter (first, orderBy, minTrades) having its own description. The tool description adds no extra parameter context beyond the schema, so a baseline score of 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?

The description uses a specific verb ('Get') with a distinct resource ('top Polymarket traders ranked by realized P&L, win rate, or volume') and names an explicit data source ('Beefy P&L subgraph'). This clearly differentiates it from sibling tools like get_trader_profile or get_account_pnl that target individual traders.

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?

The description implies the tool is for fetching leaderboard-style data but provides no explicit when-to-use guidance or alternative tools. It only states what it does, not when to prefer it over siblings like get_trader_profile or query_subgraph.

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