Skip to main content
Glama

Search large stablecoin transfers in recent blocks

crypto_whales
Read-only

Large stablecoin and major-token transfers in the last few minutes on Ethereum, Base, Arbitrum, Optimism or Polygon: hash, block time, sender, receiver, amount and USD value at the Coinbase spot price, sorted by value. Labels only for a few known addresses; others are null. One token contract is read over public RPC, so the window is short. Information only, not financial advice. Related tools on this server, for a different need: crypto_candles when you need OHLCV candles for a Coinbase trading pair at 1m, 5m, 15m; crypto_convert when you need to convert crypto and fiat amounts at the current spot rate. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crypto_whales"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoethereum (default), base, arbitrum, optimism or polygon
limitNoTransfers to return, 1 to 50, default 20
tokenNoUSDC (default), USDT, WETH, WBTC or cbBTC, where the chain has it
blocksNoBlocks to scan back from the latest: ethereum 10 (default, max 25), base and optimism 20 (max 40), arbitrum and polygon 40 (max 80)
minUsdNoMinimum USD value per transfer, default 1000000, at least 10000

Output Schema

NameRequiredDescriptionDefault
noteNo
chainNo
tokenNo
totalNo
minUsdNo
sourceNo
windowNo
scannedNo
decimalsNo
priceUsdNo
returnedNo
checkedAtNo
transfersNo
truncatedNo
disclaimerNo
tokenAddressNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses that address labels are mostly null, that only one token contract is read over public RPC so the window is short, and the exact cost model ($0.003 per successful call via x402, failed calls not charged). Data-quality caveats and the billing failure mode are exactly the behavior an agent cannot get from 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?

Scope, caveats, alternatives, and pricing arrive in a sensible order with no wasted lead-in. The 'Information only, not financial advice' sentence and the extended payment-network enumeration are boilerplate that could be trimmed without losing call-relevant information.

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 and full parameter coverage, the description concentrates on what structured fields can't carry: coverage limits, label sparsity, chain constraints, and cost. The one gap is whether results aggregate across chains or reflect a single chain per call, which matters for a 5-chain tool.

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 chain, limit, token, blocks, and minUsd are already fully documented with defaults and maxima. The description adds only return-side semantics (USD value at Coinbase spot price, sorted by value), not parameter meaning beyond the schema, so the 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?

The description names a specific resource (large stablecoin and major-token transfers), the chains covered, and the fields returned (hash, block time, sender, receiver, amount, USD value), sorted by value. An agent can immediately distinguish it from price/candle tools without opening the 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?

It explicitly routes to two alternatives with the condition that selects each ('crypto_candles when you need OHLCV candles...', 'crypto_convert when you need to convert...'), which is clear when-to-use guidance. It stops short of stating exclusions relative to the closest sibling (evm_transfers) or when this tool is the wrong choice for historical/large-window analysis.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources