wallet-tracker

get_token_holders

Read-only

The tracked wallets holding a token, sorted by balance, with market cap and
price in USD on Solana. Use when the user asks who is still holding, rather
than who ever traded it.

blockchain: solana, bnb, base, eth or rh
mint: token address
wallet_type: restrict to kol, smart or whale. Omit to merge all types.
limit: how many holders (default 25)

Input Schema

Name	Required	Description
`mint`	Yes	Token address: the mint on Solana, the contract address on the EVM chains.
`limit`	No	How many entries to return. Keep it small: large results are trimmed to fit the context window anyway.
`blockchain`	Yes	Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2.
`wallet_type`	No	Restrict to one wallet type: kol, smart or whale. Leave empty to merge all types the chain has.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / blockchain / description

Previous value: -"Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base and rh have kol and smart; eth has kol only. rh is Robinhood Chain, an Ethereum L2."New value: +"Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2."

Changed7 schema fields changedJul 27, 2026

addedInput schema / properties / blockchain / description

Added value: +"Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base and rh have kol and smart; eth has kol only. rh is Robinhood Chain, an Ethereum L2."

addedInput schema / properties / limit / description

Added value: +"How many entries to return. Keep it small: large results are trimmed to fit the context window anyway."

addedInput schema / properties / limit / maximum
```
Added value: +200
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

addedInput schema / properties / mint / description

Added value: +"Token address: the mint on Solana, the contract address on the EVM chains."

addedInput schema / properties / wallet_type / description

Added value: +"Restrict to one wallet type: kol, smart or whale. Leave empty to merge all types the chain has."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "get_token_holdersDictOutput",
+  "type": "object"
+}

AddedJul 27, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful non-obvious context the annotations lack: result ordering (by balance), the USD market cap/price fields, and per-chain wallet-type availability (solana has kol/smart/whale; others only kol/smart).

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?

Front-loaded with purpose and usage in the first two sentences, followed by a compact per-parameter reference block. Every line is short, though the parameter block partly duplicates the schema rather than adding value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With two required params, full schema coverage, and an output schema present, the description needn't explain return values. It still notes ordering and the key output fields, and the chain/wallet-type interaction, so an agent has everything needed to call it correctly.

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 every parameter is already documented in the schema. The description mostly restates those same facts (chain list, default limit 25, wallet_type options) rather than adding new meaning. Baseline 3 applies.

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?

States a specific verb+resource: tracked wallets holding a token, sorted by balance, with market cap and price in USD. The clause 'who is still holding, rather than who ever traded it' cleanly separates it from trade/transaction-oriented siblings like get_recent_trades or get_token_transactions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly frames the triggering question ('who is still holding') and contrasts it with 'who ever traded it', which routes the agent away from transaction tools. It does not name the exact sibling to use instead, keeping it just short of a 5.

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

All wallet-tracker tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?