Skip to main content
Glama

wallet-tracker

by xyz.cabalspy
OverviewDiscussionsAdmin

get_wallet_holdings

Read-only
Current onchain token holdings of a wallet, read live rather than derived from
tracked trades. Slower than the other wallet tools, often over a second. If
'loading' is true the data is still warming up — call again shortly.

blockchain: solana, bnb, base, eth or rh
address: the wallet address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesWallet address. Base58 on Solana, 0x-prefixed hex on the EVM chains.
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Wallet address. Base58 on Solana, 0x-prefixed hex on the EVM chains."
    • 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."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "get_wallet_holdingsDictOutput",
+  "type": "object"
+}
  2. Changed5 schema fields changed
    • removedInput schema / properties / address / description
      Removed value: -"Wallet address (Solana base58 or 0x… for EVM chains)."
    • removedInput schema / properties / address / examples
      Removed value: -[
-  "G6fUXjMKPJzCY1rveAE6Qm7wy5U3vZgKDJmN1VPAdiZC"
-]
    • removedInput schema / properties / blockchain / description
      Removed value: -"Blockchain network: solana, bnb, base or eth."
    • removedInput schema / properties / blockchain / examples
      Removed value: -[
-  "solana"
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "get_wallet_holdingsDictOutput",
-  "type": "object"
-}New value: +null
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds genuinely useful behavioral context: latency ('often over a second') and the async warm-up semantics where a 'loading' flag means data is incomplete and the call should be repeated. That retry guidance is not derivable from structured fields.

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 core purpose and latency/retry notes, all of which earn their place. The trailing 'blockchain: ...' and 'address: ...' lines are redundant with the schema and slightly dilute an otherwise tight description.

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 needn't be explained, and the description covers purpose, latency, and the loading-retry edge case. The only gap is the absence of explicit sibling routing, which the usage dimension already flags.

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 entries are actually richer than the description (per-chain wallet-type breakdown, Base58 vs 0x address formats). The description's trailing parameter lines restate the schema without adding meaning, so the baseline 3 applies.

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 verb and resource ('current onchain token holdings of a wallet') and immediately distinguishes it from siblings by contrasting live reads with data 'derived from tracked trades.' An agent can tell it apart from get_wallet_tracker or lookup_wallet without opening a schema.

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

Usage Guidelines3/5

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

The live-vs-derived framing implies when this tool is preferable, and the 'slower than the other wallet tools' note warns of a cost tradeoff. However, it never explicitly names an alternative or states a when-to-use condition, leaving the agent to infer the choice.

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