Skip to main content
Glama

whale-data

by com.coinlobster
OverviewDiscussionsAdmin

DEX whale board

dex_board
Read-onlyIdempotent

The wallets that moved the most size on DEXes across Ethereum, Base and Arbitrum in the last 48h, ranked, with buy and sell dollars, chains, token count and a behaviour classification; or, with token, the 24h whale-swap snapshot for one token. Use it for "who is moving size on chain", "biggest DEX traders this week", "who is trading PEPE on chain". Keyless returns the board with wallet addresses withheld; Starter and up names every wallet (pass one to dex_wallet). Descriptive market data only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoRestrict to one chain: ethereum, base, arbitrum. Anything else is refused by name rather than answered as nothing happening there. Omit for all of them.
limitNoMax wallets. Defaults to 20, hard ceiling 100 for everyone.
tokenNoOne token symbol or contract address for the per-token snapshot. Omit for the wallet board.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoRows returned.
summaryNoThe answer in one plain sentence, computed from the fields below. Open the reply with this, then let the numbers back it up. Null only when there was nothing to summarise.
upgradeNoPresent only when identities were withheld.
walletsNoRanked wallets: swaps, usd, buy_usd, sell_usd, chains, tokens, classification; wallet address on Starter and up.
snapshotNoWith token: the 24h whale-swap snapshot for that token.
availableNoFalse when the board has not published (building:true) or the token has no snapshot.
wallets_withheldNoFree: wallet identities held back on this many rows.

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 mark read-only/idempotent; the description adds useful behavior beyond that: Keyless results withhold wallet addresses, Starter+ names wallets, and the data is 'descriptive market data only'. This clarifies access-tier behavior and non-actionable nature without overclaiming.

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?

Three dense sentences, all front-loaded with the core resource first, then usage examples and access caveats. No filler or repetition of schema fields.

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?

For a 3-parameter tool with an output schema and safety annotations, the description covers the two modes, chains, time window, returned fields, access tiers, and next-step routing. Nothing essential is missing for tool selection and 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 coverage is 100%, so the baseline is 3. The description adds value by explaining the token mode ('24h whale-swap snapshot') and board mode, but it does not add new meaning for chain or limit beyond the schema descriptions.

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?

Description names a specific resource (DEX whale board), scope (Ethereum, Base, Arbitrum, last 48h), content (ranked wallets with buy/sell dollars, chains, token count, behavior classification) and the per-token mode. This gives enough specificity to distinguish it from CEX whale boards and the dex_wallet sibling.

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?

Provides explicit example queries ('who is moving size on chain', 'who is trading PEPE on chain') and explains the token mode vs wallet-board mode. It also routes wallet-level detail to dex_wallet, but does not explicitly state when not to use this tool versus other whale/DEX siblings.

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

All whale-data 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