Skip to main content
Glama

wallet-tracker

by xyz.cabalspy
OverviewDiscussionsAdmin

compare_tokens

Read-only
Statistics for up to 100 tokens in a single request. Use for shortlists, or to
follow up on the most-traded analytics view.

blockchain: solana, bnb, base, eth or rh
mints: up to 100 token addresses
wallet_type: kol, smart or whale (default kol)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mintsYesUp to 100 token addresses. Use for shortlists, or to follow up on the most_traded analytics view.
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.
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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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 / mints / description
      Added value: +"Up to 100 token addresses. Use for shortlists, or to follow up on the most_traded analytics view."
    • addedInput schema / properties / mints / maxItems
      Added value: +100
    • 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_tokensDictOutput",
+  "type": "object"
+}
  2. Added

TDQS

B3.4/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 safety is covered. The description adds the batch ceiling (100) and chain/wallet-type constraints, but does not disclose cost, rate limits, or any behavior beyond what annotations plus schema already convey.

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?

Front-loaded with the scope statement, and the parameter list is compact. The three-line param block largely duplicates the schema enums verbatim, which is mildly wasteful but not bloated.

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?

An output schema exists, so return values need not be explained, and the description covers batch size, supported chains, and wallet types. The remaining gap is that 'statistics' is never named, and no sibling is referenced for contrast.

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 is in fact richer than the description (it documents which chains support which wallet types, and notes rh is Robinhood Chain). The description's parameter list is essentially a restatement of the schema, adding no new semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Statistics for up to 100 tokens in a single request', which conveys the resource (tokens) and batching scope but uses a noun phrase rather than a clear verb and never specifies which statistics are returned. It is distinguishable from single-token siblings only by the 'up to 100' batch limit, and it does not differentiate itself from compare_wallets by name.

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 concrete usage contexts: 'Use for shortlists, or to follow up on the most-traded analytics view.' This tells the agent when the tool is appropriate, though it does not name a specific sibling (e.g. get_token_stats) as the non-batch alternative.

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