Skip to main content
Glama
pumpfun-claims-bot

pumpfun-claims-bot

by nirholas

get_token_holders

Fetch top holders for a PumpFun token and view concentration metrics to assess holder distribution and token risk.

Instructions

Fetch top holders for a PumpFun token including concentration metrics

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": "get_token_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesToken mint address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.5
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.4

TDQS

B3.2/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 full behavioral burden; 'fetch' weakly implies a read-only call and 'including concentration metrics' hints at the returned payload, which matters since there is no output schema. However, it says nothing about how many holders are returned, ordering, freshness, rate limits, or behavior for tokens with few holders.

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 padding or redundancy. It is efficient, though its brevity leaves several gaps that a second sentence could have closed.

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 single-parameter lookup this is close to adequate, but with no annotations and no output schema the description should say more about what comes back (number of holders, what concentration metrics mean, pagination or limits). As written an agent can call it but cannot predict the response.

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?

Only one parameter (mint), and the schema already documents it at 100% coverage as 'Token mint address'. The description adds only the PumpFun scoping context, which slightly clarifies the expected chain/address family but is baseline-level value.

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?

States a specific verb and resource (fetch top holders) scoped to PumpFun tokens, plus the added output feature of concentration metrics. That distinguishes it clearly from siblings like get_token_info and get_token_trades, though 'top' is left undefined (no count or threshold).

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 when an agent should prefer get_token_info or get_token_trades instead. The agent must infer the use case entirely from the name and one-line purpose.

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