Skip to main content
Glama

Trading Signals Toolkit

Crypto Whale Flow

whale_flow
Read-only

Call before chasing or fading a Base or Solana token move, to see if big wallets are buying or dumping. Large DEX trades from the last 1-24h in the token's top 3 pools: whale buy vs sell USD, net flow and % of liquidity, accumulation / distribution signal, hourly flow, largest trades with wallets, top accumulators and distributors. Solana adds Jupiter buy/sell volume. No CEX in/outflows. Read-only, never places orders. Informational only, not investment advice.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token": "<token>"
    },
    "name": "whale_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain (default: detected from the token format)
hoursNoLook-back window in hours (default 24)
tokenYesToken address: Base ERC-20 0x… or Solana mint (base58)
minUsdNoMinimum trade size in USD (default: auto from liquidity and volume)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world, non-idempotent), and the description adds substantive coverage: the look-back band, the top-3-pools limitation, Solana Jupiter volume as an extra source, and explicit exclusion of CEX flows. It does not address latency, rate limits, or what happens when a token has no qualifying pools, and "never places orders" partially restates destructiveHint=false.

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?

Front-loaded with the decision trigger, then the payload contents, then the limitations and disclaimer. Dense but every sentence carries scope or output information, and the disclaimer is justified for a financial signal tool.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description takes on the return-value burden and discharges it by enumerating the concrete fields an agent will receive (buy vs sell USD, net flow, % of liquidity, hourly flow, largest trades, top accumulators/distributors). Required token format, chain detection and defaults are handled by the schema, leaving nothing material missing.

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%, with defaults and the chain enum already documented per parameter, so the baseline is 3. The description only echoes the 1–24h window and the liquidity-derived minimum trade size, adding no syntax or tuning guidance beyond the schema.

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?

States a specific action and resource: reading large DEX trades in a token's top 3 pools to judge whether large wallets are buying or dumping. It also strictly defines scope — Base and Solana spot DEX only, exclusive of CEX in/outflows — so an agent can separate it from verdict/pre-trade siblings without opening a 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?

Gives a real trigger: call it before chasing or fading a token move. The negative scope ("No CEX in/outflows") and the informational-only framing tell the agent when the output is not sufficient on its own, but no sibling tool is named as an alternative even though token_verdict, token_pre_trade and solana_token_verdict appear in the catalog.

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