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

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 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 / 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 / mint / description

Added value: +"Token address: the mint on Solana, the contract address on the EVM chains."

addedInput schema / properties / wallet_type / description

Added value: +"Restrict to one wallet type: kol, smart or whale. Leave empty to merge all types the chain has."

changedOutput schema / (root)

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

AddedJul 27, 2026

TDQS

A3.6/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 description usefully adds result ordering (most recent first) and the default limit, but says nothing about pagination, rate limits, or truncation beyond what the schema already notes.

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?

Opening sentence is front-loaded with purpose and ordering, and the use-case line adds value. The trailing per-parameter list duplicates schema content, slightly diluting conciseness.

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 described; the description covers ordering, defaults, and chain/wallet-type caveats. An agent has enough to call it correctly, though exclusions vs. sibling trade-listing tools remain unstated.

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 all four parameters are already documented in the schema, including enum-like values and the merge behavior for wallet_type. The description largely restates that, so the 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?

States a specific verb+resource: individual buys and sells by tracked wallets in one token, most recent first. It is clear about scope (one token) and ordering, though it does not explicitly contrast with the overlapping sibling get_recent_trades.

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 a concrete use case – reconstructing the sequence of events, e.g. whether KOLs bought before or after a price move – which tells the agent when this tool is valuable. It stops short of naming alternatives or stating when not to use it.

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?