Skip to main content
Glama

Token holders

token_holders
Read-only

Get full holder list for a Solana token with concentration analysis. Returns top holders, balances, % of supply, and distribution metrics. Costs $0.005 USDC per call.

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": {
      "mintAddress": "<mintAddress>"
    },
    "name": "token_holders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of top holders to return (default: 25)
mintAddressYesSolana token mint address (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely new context — explicit per-call pricing ($0.005 USDC) and the shape of the result (top holders, balances, % of supply, distribution metrics). It does not clarify whether the list is truncated at 'limit' or truly 'full', which is the one ambiguity left.

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?

Three short sentences, each carrying a distinct payload: what it does, what comes back, and what it costs. The core purpose is front-loaded with zero filler.

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 no output schema, the description usefully enumerates the returned fields and the cost, which is enough for an agent to decide and call. It stops short of explaining truncation/pagination relative to the limit parameter, which is the remaining gap for a list-returning tool.

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 both mintAddress (base58) and limit (default 25) are already documented. The description adds no format, range, or max guidance for limit, so it does not exceed the baseline.

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 — full holder list for a Solana token plus concentration analysis — and names the return contents. It does not explicitly contrast with the nearest sibling, holder_changes, so an agent must infer that this is a point-in-time snapshot rather than a delta.

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?

Usage is only implied by the resource ('holders of a token'). There is no statement of when to prefer this over holder_changes, smart_money, top_traders, or token_risk_score, all of which overlap on holder/distribution analysis. The cost note gives a weak implicit threshold for when it is worth calling.

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