Skip to main content
Glama

wallet-tracker

by xyz.cabalspy

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

TableJSON Schema
NameRequiredDescriptionDefault
modeNocluster means several wallets bought the same token, the strongest signal. entry marks fresh positions. exit marks wallets selling out.cluster
hoursNoObservation window in hours.
limitNoHow many entries to return. Keep it small: large results are trimmed to fit the context window anyway.
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.
min_walletsNoMinimum wallets in a cluster. Higher means fewer but stronger signals. 0 uses the server default of 3.
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
min_win_rateNoOnly count wallets above this historical win rate, 0 to 100. 0 disables it.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.5/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, openWorldHint), the description reveals critical behavioral traits: only first page reachable due to non-usable cursor, and smart money signals unavailable on eth. No contradiction with annotations.

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?

Well-structured with front-loaded summary, signal definitions, usage hint, caveat, and parameter list. Slightly verbose but every sentence earns its place. Good balance of detail and readability.

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?

Covers core purpose, usage, constraints, and all parameters. Warns about pagination limit. With an output schema present, return format explanation is not required. Minor gap: no guidance on handling empty results, but not critical.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameters with descriptions; the description adds extra context (e.g., which wallet types per blockchain, default min_wallets server value of 3, Robinhood Chain explanation), enhancing understanding beyond schema alone.

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?

The description clearly states it retrieves signals of tracked wallet clusters acting on tokens, and explicitly positions it for 'what should I be looking at right now,' distinguishing it from historical signal tools like get_signal_history.

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 clear usage context (current signals, 'what should I be looking at right now'), explains pagination limitation (raise limit instead of paginating), and notes unavailability on eth for smart money. Lacks explicit when-not-to-use alternatives but is otherwise strong.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct function—comparing tokens vs. wallets, detecting bundles, retrieving historical vs. current signals, etc. Overlap is minimal, and descriptions clearly differentiate similar-sounding tools.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (compare_, detect_, get_, list_, lookup_), all in snake_case, making it easy to predict and understand the purpose of each tool.

Tool Count4/5

With 21 tools, the set is slightly above the typical 'well-scoped' range, but the breadth of functionality—covering wallet stats, tokens, signals, bundles, and comparisons across multiple blockchains—warrants the number. No tool feels redundant.

Completeness5/5

The tool surface covers essentially all aspects of wallet tracking: browsing, per-wallet stats/history/holdings/connections, token-level analysis, signals, bundles, leaderboards, and activity metrics. No obvious gaps for the stated purpose.

Resources