wallet-tracker

list_wallets

Read-only

Browse the wallets CabalSpy tracks for a chain and wallet type. Use this to

answer which KOLs or smart money wallets are covered at all. Always pass a

limit; the full list runs into the thousands.



blockchain: solana, bnb, base, eth or rh

wallet_type: kol, smart or whale

limit: wallets per page (default 50)

cursor: pagination cursor from the previous response

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	How many entries to return. Keep it small: large results are trimmed to fit the context window anyway.
`cursor`	No	Pagination cursor taken from the previous response. Leave empty for the first page.
`blockchain`	Yes	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.
`wallet_type`	Yes	Wallet type. kol is a Key Opinion Leader, an influencer whose calls move markets. smart is a wallet selected for its track record. whale is a large holder, Solana only.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, which align with the 'Browse' verb. The description adds behavioral context: pagination via cursor, explanation of wallet types per chain (e.g., eth only has kol), and the warning about large result sets.

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?

The description is three sentences plus a parameter list. It is front-loaded with purpose and usage. The parameter list is somewhat redundant with the schema, but overall it remains compact and informative.

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?

Given the output schema exists, the description need not explain return values. It covers purpose, usage guidelines, parameter details, and pagination. No gaps remain for an agent to invoke the tool correctly.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds value by emphasizing the limit parameter ('Always pass a limit'), detailing which wallet types exist per blockchain, and clarifying the cursor's purpose. This goes beyond the schema descriptions.

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?

The description clearly states the tool browses wallets tracked by CabalSpy for a given chain and wallet type, specifically to check coverage of KOLs, smart money, or whale wallets. This verb ('Browse') and resource ('wallets') combination distinguishes it from sibling tools like compare_wallets or get_wallet_holdings.

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?

The description advises to always pass a limit due to potentially large lists, and implies this tool is for browsing available wallets. While it doesn't explicitly state when not to use or name alternative tools, the context makes the intended use clear.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct function—comparing tokens vs. wallets, detecting bundles, retrieving historical vs. current signals, etc. Overlap is minimal, and descriptions clearly differentiate similar-sounding tools.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (compare_, detect_, get_, list_, lookup_), all in snake_case, making it easy to predict and understand the purpose of each tool.

Tool Count4/5

With 21 tools, the set is slightly above the typical 'well-scoped' range, but the breadth of functionality—covering wallet stats, tokens, signals, bundles, and comparisons across multiple blockchains—warrants the number. No tool feels redundant.

Completeness5/5

The tool surface covers essentially all aspects of wallet tracking: browsing, per-wallet stats/history/holdings/connections, token-level analysis, signals, bundles, leaderboards, and activity metrics. No obvious gaps for the stated purpose.

Resources

Need Help?