Crypto, web, finance and app data tools

Whale Transfers

whale_transfers

Whale alerts: the largest recent ERC-20 transfers (default USDC over $1M) in the latest blocks, with sender, receiver, amount and mint/burn flag. Works for USDC, USDT, DAI or any token on 5 EVM chains.

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": "whale_transfers"
  }
}

Input Schema

Name	Required	Default
`chain`	No	ethereum
`limit`	No
`token`	No	USDC
`blocks`	No
`min_amount`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose meaningful behavioral context: the scan window is 'the latest blocks' only, the default filter is USDC over $1M, and each record carries a mint/burn flag. It does not enumerate which 5 chains are supported, nor mention rate limits, pagination, or that historical ranges are unavailable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core purpose, then the supported-token scope. No filler, no restating of the tool name or title.

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

Completeness3/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 (though the description duplicates it). For a 5-parameter, annotation-free tool with zero schema coverage, the description should at minimum name the 5 chains and clarify amount units and block-window semantics; those gaps leave an agent guessing.

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 description coverage is 0% for 5 parameters. The description explains two of them in prose ('default USDC', 'over $1M', 'latest blocks' loosely covering blocks), but leaves chain, limit, and the exact semantics of blocks/min_amount units (whole tokens vs base units) undocumented anywhere.

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?

States a specific verb and resource: 'largest recent ERC-20 transfers ... in the latest blocks', plus what each record contains. The 'whale' framing and the $1M default clearly separate it from the generic erc20_transfers sibling, though it never names that sibling explicitly.

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?

'Works for USDC, USDT, DAI or any token on 5 EVM chains' gives context on applicability, but there is no explicit statement of when to prefer this over erc20_transfers or event_logs for transfer data. Usage is implied by the whale/large-transfer framing rather than declared.

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

All Crypto, web, finance and app data tools tools Inspect

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

Need Help?