Skip to main content
Glama

wallet-tracker

by xyz.cabalspy
OverviewDiscussionsAdmin

get_wallet_history

Read-only
Lifetime trading history of a wallet: aggregate stats, a per-token overview and
the individual trades. Use for what a wallet traded historically, rather than
how it is doing now.

This endpoint returns its pagination inside the payload rather than alongside
it; follow pagination.next_cursor until it is null for a full export.

blockchain: solana, bnb, base, eth or rh
address: the wallet address
cursor: pagination cursor from the previous response
limit: trades per page, 1-1000 (default 50; higher values get trimmed anyway)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many entries to return. Keep it small: large results are trimmed to fit the context window anyway.
cursorNoPagination cursor taken from the previous response. Leave empty for the first page.
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. Changed7 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."
    • addedInput schema / properties / cursor / description
      Added value: +"Pagination cursor taken from the previous response. Leave empty for the first page."
    • 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
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "get_wallet_historyDictOutput",
+  "type": "object"
+}
  2. Changed8 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"
-]
    • removedInput schema / properties / cursor / description
      Removed value: -"Pagination cursor from the previous response. Omit for the first page."
    • changedInput schema / properties / limit / default
      Previous value: -100New value: +50
    • removedInput schema / properties / limit / description
      Removed value: -"Trades per page, 1-1000."
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "get_wallet_historyDictOutput",
-  "type": "object"
-}New value: +null
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description only needs to add traits the annotations cannot. It does: pagination lives inside the payload and next_cursor must be followed until null, and oversized limits get trimmed, both of which materially change how an agent should loop and size calls.

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 purpose sentence, a short pagination caveat, then a compact parameter glossary; every line is scannable and nothing rambles. Modest redundancy with the 100%-covered schema parameters slightly dilutes the value of the parameter block.

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, historical-vs-current scope, and the non-obvious cursor-in-payload pagination loop. The only genuine gap is the inconsistent limit range, which leaves the agent with contradictory guidance on a parameter it must set.

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 the baseline is 3, and the description largely restates the schema's blockchain/address/cursor definitions. Worse, it states limit is '1-1000 (default 50)' while the schema caps maximum at 200, a conflicting bound that could mislead an agent into requesting an out-of-range value.

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+resource (lifetime trading history of a wallet) and enumerates the three payload components: aggregate stats, per-token overview, and individual trades. The contrast 'rather than how it is doing now' implicitly separates it from the holdings/tracker siblings, so an agent can route 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 Guidelines4/5

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

Explicitly frames use as historical-trade lookup versus current-state tools ('Use for what a wallet traded historically, rather than how it is doing now'), which is clear when-to-use guidance. It stops short of naming the specific alternative sibling (e.g. get_wallet_holdings), so the routing is inferred rather than explicit.

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