Skip to main content
Glama
Sign In

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

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, 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. 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"
+}
  3. Added

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 body text adds only the aggregation scope and parameter defaults; it says nothing about rate limits, auth requirements, or result trimming (that detail lives only in the schema descriptions). Adequate but not additive.

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?

Front-loaded with the purpose and mode enumeration, and every sentence is short. The trailing parameter list is largely redundant with a 100%-covered schema, which costs it a point, but nothing is padded or buried.

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 annotations cover the safety profile. With modes, defaults and the aggregation scope all stated, an agent has enough to invoke it correctly; only explicit sibling routing is absent.

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 carries the semantics, and it is in fact richer than the description (per-chain wallet-type availability, trimming guidance for limit/period). The description's parameter list largely restates the schema, so the baseline 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?

Opens with a specific verb+resource ('Four aggregate views over the tracked wallets') and then enumerates each mode's meaning (volume_trend, most_traded, win_rate, top_performers). The closing line 'Use for the overall picture rather than one wallet or token' separates it from single-entity siblings like compare_wallets and get_wallet_tracker.

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?

Explicitly scopes the tool to aggregate/overall views rather than one wallet or token, which gives clear selection context. It does not, however, name the specific sibling tools (e.g. lookup_wallet, get_wallet_tracker, compare_wallets) that handle the per-entity case, so the routing is implied rather than spelled out.

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