Skip to main content
Glama
Sign In

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

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, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / blockchain / description
      Previous 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."New value: +"Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2."
  2. 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"
+}
  3. 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
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly/openWorld, so the bar is lower, and the description adds genuinely non-obvious behavior: pagination is embedded in the payload rather than alongside it, requiring next_cursor to be followed until null. It also notes that large limits 'get trimmed anyway', disclosing a practical response-size constraint.

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 tool's purpose, then pagination semantics, then a tight parameter glossary. Minimal waste, though the parameter block largely duplicates schema descriptions.

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 explained, and the description still adds the pagination-format caveat that is essential for correct iteration. Only the limit-range inconsistency keeps this from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3 would apply, but the description undercuts the schema by stating limit is '1-1000' while the input schema caps it at maximum 200 — a direct conflict that could lead an agent to pass invalid values. Otherwise it mostly restates what the schema already documents about blockchain and cursor.

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?

It names a specific verb+resource ('Lifetime trading history of a wallet') and enumerates the three payload parts an agent gets back (aggregate stats, per-token overview, individual trades). The clause 'rather than how it is doing now' distinguishes it from current-state siblings like get_wallet_holdings, though no sibling is named explicitly.

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 a clear temporal selection rule ('what a wallet traded historically, rather than how it is doing now') plus a concrete pagination procedure for full exports. It stops short of naming the alternative tools an agent should pick instead for present-tense questions.

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