Skip to main content
Glama

wallet-tracker

by xyz.cabalspy
OverviewDiscussionsAdmin

get_analytics

Read-only
Four aggregate views over the tracked wallets.

volume_trend shows activity over time. most_traded lists the tokens getting the
most attention. win_rate gives the distribution of outcomes. top_performers
ranks wallets by profit. Use for the overall picture rather than one wallet or
token.

blockchain: solana, bnb, base, eth or rh
mode: volume_trend, most_traded, win_rate or top_performers
wallet_type: kol, smart or whale (default kol)
period: 6h, 1d, 7d or 30d (default 7d)
limit: how many entries (default 20)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesvolume_trend shows activity over time. most_traded lists the tokens getting the most attention. win_rate gives the distribution of outcomes. top_performers ranks wallets by profit.
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.7d
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. Changed8 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 / mode / description
      Added value: +"volume_trend shows activity over time. most_traded lists the tokens getting the most attention. win_rate gives the distribution of outcomes. top_performers ranks wallets by profit."
    • 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_analyticsDictOutput",
+  "type": "object"
+}
  2. Added

TDQS

B3.4/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 the aggregate-scope framing but no behavioral context such as rate limits, data freshness, or trimming behavior (the trimming warning lives only in the schema). With annotations carrying the burden and an output schema present, this is adequate but thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is well front-loaded, but the following four lines duplicate the parameter enumerations that the schema already provides verbatim, so a meaningful portion of the text does not earn its place. Structure is orderly but redundant.

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 not be explained, and the schema fully documents parameters. The description covers the modes and usage scope, leaving it complete enough for an agent to select and call it. Only the naming of alternative tools is missing.

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 the schema already documents every parameter, and it does so more richly than the description (context-window trimming warnings for limit/period, per-chain wallet availability for blockchain). The description merely restates the option lists with defaults and adds no syntax or format detail beyond the schema. Baseline 3 is correct.

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 opening sentence names the resource ('tracked wallets') and the four aggregate modes with a specific meaning for each (volume_trend, most_traded, win_rate, top_performers). It also scopes itself against siblings ('overall picture rather than one wallet or token'), implicitly distinguishing it from get_wallet_tracker/compare_wallets. It stops short of naming the alternative tools, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

'Use for the overall picture rather than one wallet or token' gives an implied when-to-use boundary. However it never names the alternative tools (compare_wallets, get_wallet_tracker, get_leaderboard) or states when NOT to use this tool. The guidance is present but left to inference.

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