wallet-tracker

get_token_transactions

Read-only

Individual buys and sells by tracked wallets in one token, most recent first.

Use for the sequence of events, for example whether KOLs bought before or after

a price move.



blockchain: solana, bnb, base, eth or rh

mint: token address

wallet_type: restrict to kol, smart or whale. Omit to merge all types.

limit: how many transactions (default 25)

Input Schema

TableJSON Schema

Name	Required	Description
`mint`	Yes	Token address: the mint on Solana, the contract address on the EVM chains.
`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 and rh have kol and smart; eth has kol only. rh is Robinhood Chain, an Ethereum L2.
`wallet_type`	No	Restrict to one wallet type: kol, smart or whale. Leave empty to merge all types the chain has.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

TDQS

A4.7/5.0

Behavior5/5

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

Annotations indicate readOnlyHint=true and openWorldHint=true. The description adds that results are most recent first, large results are trimmed to fit context window, and blockchain-specific wallet type availability. This provides meaningful behavioral context beyond annotations.

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?

The description is remarkably concise yet informative. It front-loads the core purpose, gives a usage example, then lists parameters with clear options. Every sentence adds value, and the structure is easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema (not shown here), the description does not need to explain return values. It covers all 4 parameters, blockchain specifics, wallet type options, and limit behavior. It provides sufficient context for an AI agent to use the tool correctly.

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 coverage is 100%, so baseline is 3. The description adds value by clarifying blockchain-specific wallet types and the default limit behavior. While schema already describes parameters, the description enhances usability with examples and constraints.

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 returns individual buys and sells by tracked wallets for one token, most recent first. It provides a usage example illustrating the sequence of events, distinguishing it from sibling tools like get_token_stats or get_token_holders.

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?

The description includes a concrete use case ('Use for the sequence of events, for example whether KOLs bought before or after a price move') and lists parameters with available options, guiding when to use. It does not explicitly exclude scenarios or mention alternatives, but the context is clear.

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

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

Need Help?