Skip to main content
Glama
Sign In

wallet-tracker

by xyz.cabalspy
OverviewDiscussionsAdmin

get_recent_trades

Read-only
The live feed: what tracked wallets are buying and selling right now, across
every token or filtered to one. Use for "what are KOLs buying at the moment".

blockchain: solana, bnb, base, eth or rh
wallet_type: kol, smart or whale (default kol)
minutes: only trades from the last N minutes, at most 60. Leave at 0 for the
         most recent trades regardless of age.
mint: restrict to one token
limit: how many trades (default 25)

Input Schema

NameRequiredDescriptionDefault
mintNoRestrict the result to a single token. Leave empty for all tokens.
limitNoHow many entries to return. Keep it small: large results are trimmed to fit the context window anyway.
minutesNoOnly trades from the last N minutes, at most 60. Leave at 0 for the most recent trades regardless of age.
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.
wallet_typeNoWallet type. kol is a Key Opinion Leader, an influencer whose calls move markets. smart is a wallet selected for its track record. whale is a large holder, Solana only.kol

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. Changed10 schema fields changed
    • 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
    • addedInput schema / properties / mint / description
      Added value: +"Restrict the result to a single token. Leave empty for all tokens."
    • addedInput schema / properties / minutes / description
      Added value: +"Only trades from the last N minutes, at most 60. Leave at 0 for the most recent trades regardless of age."
    • addedInput schema / properties / minutes / maximum
      Added value: +60
    • addedInput schema / properties / minutes / minimum
      Added value: +0
    • addedInput schema / properties / wallet_type / description
      Added value: +"Wallet type. kol is a Key Opinion Leader, an influencer whose calls move markets. smart is a wallet selected for its track record. whale is a large holder, Solana only."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "get_recent_tradesDictOutput",
+  "type": "object"
+}
  3. Added

TDQS

A3.6/5.0
Behavior3/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 the real-time/'right now' character of the feed, which is genuine behavioral context, but says nothing about refresh cadence, data latency, or cost. Adequate but thin beyond 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?

Purpose is front-loaded in the first sentence, followed by a compact one-line-per-parameter legend that scans fast. The parameter list duplicates schema text, so a little of it does not earn its place, but nothing is bloated.

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?

An output schema exists, so return-value explanation is not required, and the description covers the tool's real-time semantics plus every parameter. It leaves minor gaps (pagination/refresh behavior, what set of wallets counts as 'tracked'), but nothing that would cause a mis-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 description coverage is 100%, so the schema already documents all five parameters in detail (including the richer per-chain wallet-type availability and the 'rh is Robinhood Chain' note). The description's parameter legend largely restates the schema and adds no syntax or format meaning the agent could not already read. Baseline 3 applies.

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 names a specific resource and its defining trait ('the live feed: what tracked wallets are buying and selling right now'), which is a real functional distinction from historical siblings like get_wallet_history or get_token_transactions. It stops short of naming any sibling explicitly, so differentiation is inferable rather than stated.

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 concrete usage cue, 'Use for "what are KOLs buying at the moment"', which tells the agent the intent this tool serves. There is no when-not guidance and no named alternative to route against, so it stays at clear-context level rather than full routing guidance.

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