Skip to main content
Glama

wallet-tracker

by xyz.cabalspy
OverviewDiscussionsAdmin

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
NameRequiredDescriptionDefault
limitNoHow many entries to return. Keep it small: large results are trimmed to fit the context window anyway.
cursorNoPagination cursor taken from the previous response. Leave empty for the first page.
blockchainYesBlockchain. 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_typeYesWallet 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
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • 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 / cursor / description
      Added value: +"Pagination cursor taken from the previous response. Leave empty for the first page."
    • 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 / wallet_type / description
      Added value: +"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."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "list_walletsDictOutput",
+  "type": "object"
+}
  2. Changed7 schema fields changed
    • removedInput schema / properties / blockchain / description
      Removed value: -"Blockchain network: solana, bnb, base or eth."
    • removedInput schema / properties / blockchain / examples
      Removed value: -[
-  "solana"
-]
    • removedInput schema / properties / cursor / description
      Removed value: -"Pagination cursor from the previous response. Omit for the first page."
    • removedInput schema / properties / limit / description
      Removed value: -"Max number of wallets per page."
    • removedInput schema / properties / wallet_type / description
      Removed value: -"Wallet category: kol, smart or whale."
    • removedInput schema / properties / wallet_type / examples
      Removed value: -[
-  "kol"
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "list_walletsDictOutput",
-  "type": "object"
-}New value: +null
  3. First observed

TDQS

A4/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 classification is known. The description adds genuinely non-redundant behavior: the result set is unbounded in size (thousands) and paginated via cursor from the previous response, which is not visible in the annotations.

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?

Purpose and the key limit constraint are front-loaded, and the trailing parameter block is terse. That block partially restates what the schema already documents, which is mild redundancy rather than bloat.

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?

An output schema exists, so return values need no explanation. The description covers discovery scope, the size/pagination behavior, and the required limit, though it omits the chain-wallet_type compatibility rules (e.g., whale is Solana-only) that the schema does carry.

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 description coverage is 100%, so the baseline is 3. The description adds a usage directive on limit ('Always pass a limit') and compresses the valid blockchain/wallet_type values into a quick reference, slightly exceeding the schema's contribution.

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?

The description uses a specific verb and resource ('Browse the wallets CabalSpy tracks') and scopes it by chain and wallet type, making the enumeration role clear against per-wallet siblings like lookup_wallet. It never names an alternative tool explicitly, so differentiation is functional rather than stated.

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?

'Use this to answer which KOLs or smart money wallets are covered at all' gives a concrete use case, and 'Always pass a limit; the full list runs into the thousands' is actionable guidance. No when-not condition or named alternative is provided, so it stops short of a full routing rule.

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

All wallet-tracker toolsInspect
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