Skip to main content
Glama
Polymarket MCP Server

Polymarket MCP Server

by yashhsm

get_top_holders

Retrieve top holders for specified Polymarket markets, with optional holder limit and minimum balance threshold.

Instructions

Get top holders for specified Polymarket markets

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": {
      "market": "<market>"
    },
    "name": "get_top_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax number of holders to return
marketYesCondition IDs (required)
minBalanceNoMinimum balance threshold

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: it does not say how holders are ranked, whether results are paginated, whether it requires authentication, or what the result shape is. Only the word 'top' hints at ordering.

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 wasted words. It is efficient, though it is efficient partly because it omits useful detail.

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?

For a simple three-parameter read tool with fully documented schema, the definition is minimally sufficient. The lack of any output schema means the agent gets no signal about ranking basis, response size, or ordering, which is a real gap despite the tool's simplicity.

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 the schema already documents market as condition IDs, limit as max holders, and minBalance as a threshold. The description adds no format or constraint detail beyond 'specified markets', so the baseline of 3 applies.

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?

Names a specific verb and resource ('Get top holders') scoped to Polymarket markets, which an agent can distinguish from get_leaderboard or get_market_by_slug. It stops short of explaining what 'top' means, but the core purpose is unambiguous.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as get_leaderboard for cross-market rankings. The agent must infer selection criteria entirely from the name.

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