Skip to main content
Glama

Base whale transfers (x402)

Largest token transfers (whale movements) on Base in the last minutes to hour: the biggest ERC-20 Transfer events of a t

base_token_large_transfers
Read-onlyIdempotent

Largest token transfers (whale movements) on Base in the last minutes to hour: the biggest ERC-20 Transfer events of a token over a window of up to 1,000 blocks with amount, sender, receiver and transaction hash, filtered by a minimum amount (token=0x..., min_amount, blocks=400, count=20). For trading and risk agents watching large flows. Pay per call $0.02 USDC on Base via x402.

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

Input Schema

NameRequiredDescriptionDefault
countNohow many, 1-50, default 20
tokenNoERC-20 token address on Base, 0x...
blocksNorecent blocks 50-1000, default 400 (about 2 s each)
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements
min_amountNominimum transfer size in tokens, default 0

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly/idempotent/non-destructive/open-world, so the baseline is low, and the description still contributes real behavioral context: the per-call price ($0.02 USDC on Base via x402) and the payment dance ('omit x_payment on the first call to receive the price and payment requirements'). That auth/payment flow is non-obvious and critical for an agent to call this successfully.

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 resource and window before the parameter example and the payment note, and every fragment carries information. The opening sentence is long and carries a parenthetical example call, which makes it denser than ideal, but there is no filler.

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?

For a five-param, no-required, read-only query with no output schema, the description covers the returned fields, the time window semantics, the min-amount filter, and the payment prerequisite. The only real gap is the exact response shape/pagination, which is minor for a single-shot list query.

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%, so all five parameters including defaults and ranges are already documented in structured form. The description only restates the filter intent (minimum amount, block window) and gives a sample call; it adds little syntax or format meaning beyond the schema.

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?

Names a specific resource and scope: 'biggest ERC-20 Transfer events of a token over a window of up to 1,000 blocks' with the returned fields (amount, sender, receiver, transaction hash). The 'whale movements' framing makes it clearly distinct from price/contract-check style siblings, though it never explicitly contrasts itself with any named sibling tool.

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?

Provides a target audience statement ('For trading and risk agents watching large flows') and a concrete example invocation, which implies the use case. It stops short of saying when to prefer this over alternatives (e.g. swap-level or price tools) or any explicit exclusions.

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