Skip to main content
Glama

wallet-tracker

by xyz.cabalspy
OverviewDiscussionsAdmin

get_wallet_connections

Read-only
Other tracked wallets that traded the same tokens as this one over the last 30
days, ranked by overlap. Useful for finding groups that move together, which
can indicate coordination.

blockchain: solana, bnb, base, eth or rh
address: the source wallet address
limit: how many connections (default 25)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many entries to return. Keep it small: large results are trimmed to fit the context window anyway.
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. Changed6 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 / 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_connectionsDictOutput",
+  "type": "object"
+}
  2. 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"
-]
    • changedInput schema / properties / limit / default
      Previous value: -50New value: +25
    • removedInput schema / properties / limit / description
      Removed value: -"Max number of connections to return."
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "get_wallet_connectionsDictOutput",
-  "type": "object"
-}New value: +null
  3. First observed

TDQS

A3.7/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 the safety profile is covered. The description adds meaningful behavioral constraints beyond the annotations: the 30-day lookback window, the ranking criterion (overlap), and the fact that only tracked wallets are considered. It does not contradict the annotations.

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?

The core explanation is two front-loaded sentences that earn their place. The trailing parameter legend is partially redundant given full schema coverage, but the overall definition stays short and readable.

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, the return format need not be described here. Annotations cover the safety profile, all three parameters are documented, and the description supplies the key scoping behavior (tracked wallets, 30-day window, ranked by overlap). Complete enough for correct invocation.

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 coverage is 100% and the schema already contains richer parameter documentation, including chain-specific wallet-type notes and base58 vs hex address formats. The description's parameter legend repeats the schema without adding syntax or edge-case meaning, so baseline 3 is correct.

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?

The description clearly states what the tool returns: other tracked wallets that traded the same tokens as a source wallet over the last 30 days, ranked by overlap. This distinguishes it from siblings like compare_wallets and get_wallet_tracker, though it opens with a noun phrase rather than a verb and never explicitly contrasts itself with those alternatives.

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?

It provides an implied use case — 'finding groups that move together, which can indicate coordination' — but gives no explicit when-to-use/when-not-to-use guidance and does not name or route to alternative sibling tools.

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