wallet-tracker

get_signals

Read-only

Tokens where several tracked wallets acted within the same window.

'cluster' means multiple wallets bought the same token, which is the strongest
signal. 'entry' marks fresh positions, 'exit' marks wallets selling out. Use
this for "what should I be looking at right now".

Only the first page is reachable: this endpoint reports that more results
exist but does not return a usable cursor, so raise the limit rather than
trying to paginate. Smart money signals are unavailable on eth.

blockchain: solana, bnb, base, eth or rh
wallet_type: kol, smart or whale (default kol)
mode: cluster, entry or exit (default cluster)
hours: observation window (default 6)
min_wallets: minimum wallets in a cluster; higher means fewer, stronger signals
min_win_rate: only count wallets above this historical win rate, 0-100
limit: how many signals (default 15)

Input Schema

Name	Required	Description	Default
`mode`	No	cluster means several wallets bought the same token, the strongest signal. entry marks fresh positions. exit marks wallets selling out.	cluster
`hours`	No	Observation window in hours.
`limit`	No	How many entries to return. Keep it small: large results are trimmed to fit the context window anyway.
`blockchain`	Yes	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.
`min_wallets`	No	Minimum wallets in a cluster. Higher means fewer but stronger signals. 0 uses the server default of 3.
`wallet_type`	No	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.	kol
`min_win_rate`	No	Only count wallets above this historical win rate, 0 to 100. 0 disables it.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

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

Changed16 schema fields changedJul 27, 2026

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 / hours / description
```
Added value: +"Observation window in hours."
```
addedInput schema / properties / hours / maximum
```
Added value: +168
```
addedInput schema / properties / hours / minimum
```
Added value: +1
```

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 / min_wallets / description

Added value: +"Minimum wallets in a cluster. Higher means fewer but stronger signals. 0 uses the server default of 3."

addedInput schema / properties / min_wallets / maximum
```
Added value: +50
```
addedInput schema / properties / min_wallets / minimum
```
Added value: +0
```

addedInput schema / properties / min_win_rate / description

Added value: +"Only count wallets above this historical win rate, 0 to 100. 0 disables it."

addedInput schema / properties / min_win_rate / maximum
```
Added value: +100
```
addedInput schema / properties / min_win_rate / minimum
```
Added value: +0
```

addedInput schema / properties / mode / description

Added value: +"cluster means several wallets bought the same token, the strongest signal. entry marks fresh positions. exit marks wallets selling out."

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_signalsDictOutput",
+  "type": "object"
+}

AddedJul 27, 2026

TDQS

A3.9/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 meaningful behavior beyond them: only the first page is reachable and no usable cursor is returned, plus eth has no smart-money data. It does not mention auth requirements or rate limits, but the pagination caveat is a high-value disclosure.

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, mode semantics, and the key limitations are front-loaded before the parameter list, and prose is tight. The trailing parameter enumeration is partly redundant given full schema coverage, which keeps it from a 5.

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 the description covers purpose, mode semantics, the pagination constraint, and the eth limitation. It is close to complete for a 7-param filtered-list tool, with only minor gaps around defaults/constraints already handled by the schema.

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 descriptions are actually richer than the prose list (e.g., min_wallets '0 uses the server default of 3', limit trimming guidance). The description's parameter list largely restates the schema, so baseline 3 is appropriate.

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 description gives a specific verb+resource: tokens where multiple tracked wallets acted in the same window, and unpacks the three modes (cluster/entry/exit). The phrase 'what should I be looking at right now' implicitly separates it from the get_signal_history sibling by signaling current/latest signals, though it never names the sibling 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?

It gives clear usage context ('Use this for "what should I be looking at right now"') and an explicit when-not condition ('Smart money signals are unavailable on eth'). It also tells the agent how to handle result size (raise the limit rather than paginate). It stops short of naming alternative tools for historical lookups.

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?