Skip to main content
Glama
pump.fun MCP Server

pump.fun MCP Server

by blixtrade

top_holders

Retrieve a Solana token's largest holders with supply share, pool and insider labels, plus a concentration summary to assess holder risk.

Instructions

Top holders of a Solana token with share of supply, pool and insider labels, and concentration summary.

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": {
      "mint": "<mint>"
    },
    "name": "top_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana token mint address (base58).
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it does disclose the analytical content returned (labels, concentration summary), which helps an agent judge the value of the call. However it says nothing about read-only safety, data freshness/on-chain source, ordering of holders, or cost, all of which an unannotated tool should cover.

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 dense sentence with zero filler; the most important identification (Solana token holder ranking) comes first and the returned fields follow.

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?

With no output schema and no annotations, the description does a reasonable job of previewing return content, but it leaves the limit parameter, holder ordering, and data freshness unexplained — gaps that matter for an agent deciding how to call it.

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

Parameters2/5

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

Schema coverage is 50%: mint is documented in the schema, but limit (default 20, max 20, min 5) has no description anywhere. The description never mentions how many holders are returned or that the count is capped, so it does not compensate for the gap.

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 resource (top holders of a Solana token) and enumerates the payload — share of supply, pool/insider labels, concentration summary — which separates it from trade-oriented siblings like wallet_trades and whale_trades. It is not verb-first ('Top holders of...'), but the scope 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?

No when-to-use guidance, no prerequisites, and no mention of when a sibling such as rug_check or token_info would be preferred. The agent must infer that this is the holder-distribution tool from the title-like phrasing alone.

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