Skip to main content
Glama

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, eth has kol only.
period: 6h, 1d, 7d or 30d (default 1d)
limit: how many wallets (default 20)

Input Schema

TableJSON 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 and rh have kol and smart; eth has kol only. 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

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 / 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"
+}
  2. 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
  3. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds domain constraints (whale is Solana-only, eth is kol-only) but nothing about result size limits, trimming, or freshness of rankings – and the trimming behavior is only mentioned in the schema, not the description.

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 examples come first, followed by a compact parameter list. It is well front-loaded, though the parameter bullets duplicate what the schema already states, which slightly dilutes the value of the text.

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 full schema coverage, an output schema, and read-only annotations, the description supplies enough to call the tool correctly. The main remaining gap is routing guidance relative to the many sibling wallet/token tools.

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% and the schema already documents every parameter's meaning, defaults, and bounds (limit max 200, period windows, blockchain list). The description largely restates this, adding only the cross-parameter validity constraint, so the baseline of 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 resource and ranking behavior: 'Top tracked wallets ranked by performance for a chain, wallet type and period.' This is clearly distinct from siblings like list_wallets (enumeration) or compare_wallets (pairwise comparison), and the concrete query examples ('best Solana KOLs today') pin down the intent.

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?

Provides real usage contexts via example queries and enumerates the valid domains for each filter, which helps an agent recognize appropriate calls. However it never states when NOT to use it or names a competing sibling such as list_wallets or get_wallet_tracker, so routing guidance is incomplete.

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