wallet-tracker

get_wallet_tracker

Read-only

Period statistics for ONE wallet: realized PnL, win rate, volume, trade counts,
active tokens and win-rate distribution. The main tool for "how is this trader
doing".

blockchain: solana, bnb, base, eth or rh
address: the wallet address
period: 6h, 1d, 7d or 30d (default 1d). Longer periods return far more data
        and are trimmed harder; prefer the shortest period that answers it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`period`	No	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.	1d
`address`	Yes	Wallet address. Base58 on Solana, 0x-prefixed hex on the EVM chains.
`blockchain`	Yes	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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJul 27, 2026

addedInput schema / properties / address / description

Added value: +"Wallet address. Base58 on Solana, 0x-prefixed hex on the EVM chains."

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 / 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."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "get_wallet_trackerDictOutput",
+  "type": "object"
+}

Changed7 schema fields changedJul 27, 2026

removedInput schema / properties / address / description

Removed value: -"Wallet address (Solana base58 or 0x… for EVM chains)."

removedInput schema / properties / address / examples

Removed value: -[
-  "G6fUXjMKPJzCY1rveAE6Qm7wy5U3vZgKDJmN1VPAdiZC"
-]

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 / period / description
```
Removed value: -"Time window: 6h, 1d, 7d or 30d."
```
removedInput schema / properties / period / examples
```
Removed value: -[
-  "1d"
-]
```

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "title": "get_wallet_trackerDictOutput",
-  "type": "object"
-}New value: +null

First observedJun 3, 2026

TDQS

A4.2/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 safety profile is covered. The description adds genuinely useful behavioral context beyond that: longer periods return more data and are trimmed harder, which sets expectations about result truncation.

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

Conciseness5/5

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

Front-loads the core purpose in one clause, then lists metrics, then per-parameter notes. Every line earns its place with no filler or repetition.

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-value documentation is not required, and the description covers purpose, chains, and period trade-offs. It could say more about what 'trimmed' concretely means, but nothing critical to invoking the tool 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 each parameter is already documented in the schema, including the same period enumerations and the rh/Robinhood Chain note. The description restates these rather than adding new semantics, 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?

Names a specific resource (period statistics for ONE wallet) and enumerates the concrete metrics returned (realized PnL, win rate, volume, trade counts, active tokens, win-rate distribution). The 'ONE wallet' scoping and 'how is this trader doing' framing cleanly separates it from the compare_* and history/holdings siblings.

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?

Gives explicit usage context ('the main tool for how is this trader doing') and concrete period-selection guidance ('prefer the shortest period that answers it'). It does not, however, name any alternative tool or state when NOT to use it versus close siblings like get_wallet_history or get_pnl_calendar.

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

All wallet-tracker tools Inspect

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

Need Help?