whale-data

On-chain DEX whale swaps

onchain_whales

Read-onlyIdempotent

Executed DEX whale swaps on Ethereum, Base and Arbitrum, each carrying the wallet, the DEX, the token and the USD size. Use this to see WHO is swapping large size on chain and in what ("which wallets are buying PEPE", "large DEX swaps today"). Filter by chain, coin or minimum size. For chain-level DeFi totals use defi_summary; for one address's full history use dex_wallet; for CEX whale flow use whale_trades. Keyless. Descriptive market data only.

Input Schema

TableJSON Schema

Name	Required	Description
`coin`	No	Filter to one token symbol, for example PEPE. A pair like ETH/USD works too, the quote leg is dropped. One symbol, not a list. Omit for every token.
`pair`	No	Alias for coin.
`chain`	No	Restrict to one chain: ethereum, base, arbitrum. Anything else is refused by name rather than answered as nothing happening there. Omit for all of them.
`limit`	No	Max swaps returned. Defaults to 50, hard ceiling 200 for everyone and no plan raises it.
`min_usd`	No	Smallest swap to return, in US dollars, for example 500000 for $500K and up. Omit for everything above the size floor this feed already records, which is not every swap on chain.
`since_ms`	No	Polling cursor: only rows newer than this Unix-ms timestamp, applied before the row cap. Pass back the next_since_ms from the previous answer so a timer never re-reads the same rows.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No	One line saying what the numbers cover, or why there are none. Read it before reporting any zero as a market reading.
`count`	No	How many rows this reply carries.
`swaps`	No	The swaps, each carrying the wallet that signed it, the exchange it went through, the token and the dollar size.
`capped`	No	Present only when an argument was cut down to a ceiling. Absent means nothing was clamped, so a smaller number than you asked for is the data and not a limit.
`available`	No	False when this lane could not answer: a producer is dark, the pair sits outside this plan, or the argument named something we do not carry. Absent or true means the numbers are a real reading, not a guess.
`access_note`	No	What this connection could not return and what lifts it. Always pass this on to the user: it is the only place that information appears.
`unknown_chain`	No	Set when a chain was named that this feed does not index. Nothing was searched, so this is not no swaps there.
`chains_covered`	No	The chains this feed indexes.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 5, 2026

addedInput schema / properties / since_ms

Added value: +{
+  "description": "Polling cursor: only rows newer than this Unix-ms timestamp, applied before the row cap. Pass back the next_since_ms from the previous answer so a timer never re-reads the same rows.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

Changed5 schema fields changedAug 13, 2026

addedInput schema / properties / chain / description

Added value: +"Restrict to one chain: ethereum, base, arbitrum. Anything else is refused by name rather than answered as nothing happening there. Omit for all of them."

addedInput schema / properties / coin / description

Added value: +"Filter to one token symbol, for example PEPE. A pair like ETH/USD works too, the quote leg is dropped. One symbol, not a list. Omit for every token."

addedInput schema / properties / limit / description

Added value: +"Max swaps returned. Defaults to 50, hard ceiling 200 for everyone and no plan raises it."

addedInput schema / properties / min_usd / description

Added value: +"Smallest swap to return, in US dollars, for example 500000 for $500K and up. Omit for everything above the size floor this feed already records, which is not every swap on chain."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "access_note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "What this connection could not return and what lifts it. Always pass this on to the user: it is the only place that information appears."
+    },
+    "available": {
+      "anyOf": [
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "False when this lane could not answer: a producer is dark, the pair sits outside this plan, or the argument named something we do not carry. Absent or true means the numbers are a real reading, not a guess."
+    },
+    "capped": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "applied": {
+              "description": "The value actually used.",
+              "type": "number"
+            },
+            "argument": {
+              "description": "Which argument was cut down, for example limit or hours.",
+              "type": "string"
+            },
+            "by": {
+              "description": "Why it was cut: keyless for the free ceiling, plan_max for a paid ceiling, tool_max for a ceiling no plan raises.",
+              "type": "string"
+            },
+            "max": {
+              "description": "The ceiling that applied.",
+              "type": "number"
+            },
+            "requested": {
+              "description": "The value the caller asked for.",
+              "type": "number"
+            }
+          },
+          "required": [
+            "argument",
+            "requested",
+            "applied",
+            "max",
+            "by"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Present only when an argument was cut down to a ceiling. Absent means nothing was clamped, so a smaller number than you asked for is the data and not a limit."
+    },
+    "chains_covered": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The chains this feed indexes."
+    },
+    "count": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "How many rows this reply carries."
+    },
+    "note": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "One line saying what the numbers cover, or why there are none. Read it before reporting any zero as a market reading."
+    },
+    "swaps": {
+      "anyOf": [
+        {
+          "items": {},
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The swaps, each carrying the wallet that signed it, the exchange it went through, the token and the dollar size."
+    },
+    "unknown_chain": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Set when a chain was named that this feed does not index. Nothing was searched, so this is not no swaps there."
+    }
+  },
+  "type": "object"
+}

First observedAug 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful context beyond that: it is keyless, it returns descriptive market data only, and the min_usd schema note clarifies the feed records a size floor rather than every swap. This is useful behavioral context without contradicting the annotations.

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?

Every sentence earns its place: purpose, data contents, usage examples, sibling routing, and access constraints. It is front-loaded with what the tool returns and remains compact despite covering a lot of guidance.

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 read-only list tool with a rich input schema and an output schema, the description covers the essential context: what the data is, who it is for, how to filter, which sibling to choose instead, and that no key is needed. There are no critical gaps an agent would need to infer.

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 the schema already documents every parameter in detail, including the pair alias, chain refusal behavior, limit cap, min_usd floor, and since_ms polling cursor. The description adds only a high-level grouping ('Filter by chain, coin or minimum size'), which is correct but not substantial on top of 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 ('Executed DEX whale swaps') with the resource scope ('on Ethereum, Base and Arbitrum') and the key data each result carries (wallet, DEX, token, USD size). It distinguishes itself from siblings by naming use cases and alternatives, so an agent can tell it apart before inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use guidance with natural-language examples ('which wallets are buying PEPE', 'large DEX swaps today') and names three alternatives with their specific conditions: defi_summary for chain-level totals, dex_wallet for one address history, and whale_trades for CEX flow. Also notes keyless access, which sets expectations for invocation.

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

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