Skip to main content
Glama
Sign In

wallet-tracker

by xyz.cabalspy
OverviewDiscussionsAdmin

get_leaderboard

Read-only
Top tracked wallets ranked by performance for a chain, wallet type and period.
Use for "best Solana KOLs today", "top whales this week", and similar.

blockchain: solana, bnb, base, eth or rh
wallet_type: kol, smart or whale. whale is Solana only.
period: 6h, 1d, 7d or 30d (default 1d)
limit: how many wallets (default 20)

Input Schema

NameRequiredDescriptionDefault
limitNoHow many entries to return. Keep it small: large results are trimmed to fit the context window anyway.
periodNoStatistics window: 6h, 1d, 7d or 30d. Longer windows return far more data and get trimmed harder, so prefer the shortest window that answers the question.1d
blockchainYesBlockchain. 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_typeNoWallet 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.kol

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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."
  2. 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 / 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 / period / description
      Added value: +"Statistics window: 6h, 1d, 7d or 30d. Longer windows return far more data and get trimmed harder, so prefer the shortest window that answers the question."
    • 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": "get_leaderboardDictOutput",
+  "type": "object"
+}
  3. Changed8 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 / limit / description
      Removed value: -"Max number of wallets to return."
    • removedInput schema / properties / period / description
      Removed value: -"Time window: 6h, 1d, 7d or 30d."
    • removedInput schema / properties / period / examples
      Removed value: -[
-  "1d"
-]
    • 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": "get_leaderboardDictOutput",
-  "type": "object"
-}New value: +null
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true and openWorldHint=true already tell the agent this is a safe, live-data read, so the description need not restate safety. It adds some scope context (whale is Solana-only, defaults) but nothing about result shape, freshness, or trimming beyond what the schema already covers.

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 statement is front-loaded, followed by usage examples, then a compact parameter legend. It is appropriately sized, though the parameter enumeration duplicates schema content and takes space without adding value.

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 an output schema present, return values need not be explained, and annotations cover the safety profile. Required/optional params, defaults and enum values are all available; the definition is complete enough to invoke correctly, missing only sibling-level routing.

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 all four parameters (including valid enum values and defaults) are already documented. The description's parameter list largely restates the schema, adding no syntax or semantic detail beyond it – the baseline 3 applies.

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 – "top tracked wallets ranked by performance" – scoped by chain, wallet type and period. It is clearly a ranking/leaderboard over wallets rather than a plain wallet listing (list_wallets) or token comparison (compare_tokens), though it never names a sibling to draw that boundary explicitly.

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?

Concrete example queries ("best Solana KOLs today", "top whales this week") make the intended use case easy to match against a user request. No when-not guidance or explicit alternative tool (e.g. csid_leaderboard, list_wallets) is given, so the agent must infer the boundary.

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