Skip to main content
Glama
Sign In

wallet-tracker

by xyz.cabalspy
OverviewDiscussionsAdmin

get_wallet_tracker

Read-only
Period statistics for ONE wallet: realized PnL, win rate, volume, trade counts,
active tokens and win-rate distribution. The main tool for "how is this trader
doing".

blockchain: solana, bnb, base, eth or rh
address: the wallet address
period: 6h, 1d, 7d or 30d (default 1d). Longer periods return far more data
        and are trimmed harder; prefer the shortest period that answers it.

Input Schema

NameRequiredDescriptionDefault
periodNoStatistics 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.1d
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. Changed4 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 / 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."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "get_wallet_trackerDictOutput",
+  "type": "object"
+}
  3. Changed7 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 / period / description
      Removed value: -"Time window: 6h, 1d, 7d or 30d."
    • removedInput schema / properties / period / examples
      Removed value: -[
-  "1d"
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "get_wallet_trackerDictOutput",
-  "type": "object"
-}New value: +null
  4. First observed

TDQS

A4/5.0
Behavior4/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 real behavioral context beyond that: longer periods return far more data and are 'trimmed harder', which warns the agent about result truncation. It still says nothing about auth or rate limits, but the trimming datum is genuine added value.

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-loads the purpose in the first sentence, then the one-line-per-parameter layout is scannable and wastes little. Slightly verbose in repeating the period caveat that also lives in the schema, but nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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-shape explanation is unnecessary. With required params, enums-in-description and the trimming caveat all conveyed, the definition gives an agent everything needed to invoke the tool correctly.

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 schema already documents all three parameters in detail (including the same period/trimming note and address format). The description restates blockchain, address and period without adding syntax or constraints the schema lacks; 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+resource ('Period statistics for ONE wallet') and enumerates exactly what is returned: realized PnL, win rate, volume, trade counts, active tokens and win-rate distribution. The 'ONE wallet' emphasis and 'main tool for how is this trader doing' framing meaningfully distinguish it from the multi-wallet sibling compare_wallets.

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?

Usage is implied by 'The main tool for how is this trader doing', but there is no explicit statement of when to prefer this over get_wallet_history, get_pnl_calendar, or compare_wallets. The period advice ('prefer the shortest period that answers it') is a useful calling guideline but is scoped to one parameter rather than the tool-level decision.

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