wallet-tracker

compare_wallets

Read-only

Statistics for up to 100 wallets in a single request. Much cheaper than calling
get_wallet_tracker repeatedly. Use when the user names several wallets, or to
follow up on a leaderboard.

blockchain: solana, bnb, base, eth or rh
addresses: up to 100 wallet addresses
wallet_type: kol, smart or whale (default kol)
period: 6h, 1d, 7d or 30d (default 7d)

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.	7d
`addresses`	Yes	Up to 100 wallet addresses. Far cheaper than calling get_wallet_tracker once per wallet.
`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	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

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedJul 27, 2026

addedInput schema / properties / addresses / description

Added value: +"Up to 100 wallet addresses. Far cheaper than calling get_wallet_tracker once per wallet."

addedInput schema / properties / addresses / maxItems
```
Added value: +100
```

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

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

AddedJul 27, 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 safety is covered. The description contributes a cost-model trait (much cheaper than repeated get_wallet_tracker calls), which is genuinely useful behavior beyond structured fields, though it says nothing about output volume or trimming behavior.

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

Conciseness3/5

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

The opening paragraph is tight and front-loaded, but the four-line parameter legend duplicates structured schema content that the agent already receives, so roughly half the text does not earn its place.

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 explanation is unnecessary, and the description covers batching scope, cost rationale, and when to use it. Nothing critical is missing, though output volume/trimming expectations are only hinted at in 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%, so per the rubric the baseline is 3. The description's parameter legend (blockchain/addresses/wallet_type/period) largely repeats what the schema already documents rather than adding syntax, format, or constraint detail.

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?

States a specific operation (batch statistics for up to 100 wallets in one request) with a clear resource and scope, and explicitly distinguishes itself from the sibling get_wallet_tracker by naming it as the costlier alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use conditions ('user names several wallets', 'follow up on a leaderboard') and names the alternative it replaces, so the agent can route correctly without opening schemas.

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?