DeFade — Multi-Chain Memecoin Analyzer

Whale activity

get_whales

Read-onlyIdempotent

Wallets holding at least 1% of supply once pools, lockers, treasuries and custodial accounts are removed. Each row carries the balance, share of supply, any attribution label (known KOL, dev-linked stash, exchange), the 24-hour transaction count and recent buys and sells; the summary counts dangerous and active whales and gives a whale-risk verdict. One response, no pagination; cached for 15 minutes, so activity figures can lag by that much. A token with nothing above the threshold returns an empty list and largestHumanPct, so the empty state is explainable rather than silent. Use it after get_holders when the question is about who can dump and whether they are already dumping. Not for the full ranked holder list (get_holders), historically profitable wallets (get_smart_money), or the creator's own wallet (get_dev_tracker). Arguments: address and chain; one API unit on any chain.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	No	Chain the token is deployed on: solana (default), ethereum, base, robinhood. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan.	solana
`address`	Yes	The token's own contract address, exactly as an explorer shows it. Solana: the base58 mint, 32-44 characters (e.g. 6p6xgHyF7AeE6TZkSmFsko444wqoP15icUSqi2jfGiPN). EVM: 0x followed by 40 hex characters, case-insensitive (e.g. 0x6982508145454ce325ddbe47a25d4ec3d2311933). Never a pool, pair, wallet or deployer address — those come back as not found. Set `chain` to match the address: a 0x address alone cannot say which EVM chain it lives on, and a Solana mint sent with an EVM chain is rejected.

Output Schema

TableJSON Schema

Name	Required	Description
`token`	No	The address that was scanned (on get_token_scan, the full token metadata object instead).
`whales`	No	Each whale: address, balance, percentage of supply, attribution label (notable wallet, dev-linked, exchange), txCount24h, recent buys and sells.
`summary`	No	totalWhales, totalWhalePct, dangerWhales, activeWhales, whaleRisk, whaleThreshold, largestHumanPct, protocol and Streamflow-lock totals.
`poweredBy`	No	Always "DeFade.org".
`timestamp`	No	ISO time the response was assembled.
`terminalUsage`	No	Which trading terminals the whale cohort trades through (Pro keys).
`protocolAccounts`	No	Pools, lockers, treasuries and custodial accounts held out of the whale list, named.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 12, 2026

changedOutput schema / properties / whales / description

Previous value: -"Each whale: address, balance, percentage of supply, attribution label (KOL, dev-linked, exchange), txCount24h, recent buys and sells."New value: +"Each whale: address, balance, percentage of supply, attribution label (notable wallet, dev-linked, exchange), txCount24h, recent buys and sells."

Changed6 schema fields changedSep 5, 2026

changedOutput schema / properties / poweredBy / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / protocolAccounts / type

Previous value: -"array"New value: +[
+  "array",
+  "null"
+]

changedOutput schema / properties / summary / type

Previous value: -"object"New value: +[
+  "object",
+  "null"
+]

changedOutput schema / properties / terminalUsage / type

Previous value: -"object"New value: +[
+  "object",
+  "null"
+]

changedOutput schema / properties / timestamp / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

changedOutput schema / properties / whales / type

Previous value: -"array"New value: +[
+  "array",
+  "null"
+]

Changed1 schema field changedSep 3, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "poweredBy": {
+      "description": "Always \"DeFade.org\".",
+      "type": "string"
+    },
+    "protocolAccounts": {
+      "description": "Pools, lockers, treasuries and custodial accounts held out of the whale list, named.",
+      "type": "array"
+    },
+    "summary": {
+      "additionalProperties": true,
+      "description": "totalWhales, totalWhalePct, dangerWhales, activeWhales, whaleRisk, whaleThreshold, largestHumanPct, protocol and Streamflow-lock totals.",
+      "type": "object"
+    },
+    "terminalUsage": {
+      "additionalProperties": true,
+      "description": "Which trading terminals the whale cohort trades through (Pro keys).",
+      "type": "object"
+    },
+    "timestamp": {
+      "description": "ISO time the response was assembled.",
+      "type": "string"
+    },
+    "token": {
+      "description": "The address that was scanned (on get_token_scan, the full token metadata object instead)."
+    },
+    "whales": {
+      "description": "Each whale: address, balance, percentage of supply, attribution label (KOL, dev-linked, exchange), txCount24h, recent buys and sells.",
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedSep 3, 2026

changedInput schema / properties / address / description

Previous value: -"Token contract address. A base58 mint for Solana, or 0x-prefixed for EVM chains. Set `chain` to match — a 0x address alone cannot say which EVM chain it lives on."New value: +"The token's own contract address, exactly as an explorer shows it. Solana: the base58 mint, 32-44 characters (e.g. 6p6xgHyF7AeE6TZkSmFsko444wqoP15icUSqi2jfGiPN). EVM: 0x followed by 40 hex characters, case-insensitive (e.g. 0x6982508145454ce325ddbe47a25d4ec3d2311933). Never a pool, pair, wallet or deployer address — those come back as not found. Set `chain` to match the address: a 0x address alone cannot say which EVM chain it lives on, and a Solana mint sent with an EVM chain is rejected."

changedInput schema / properties / chain / description

Previous value: -"Which chain the address lives on. Defaults to solana."New value: +"Chain the token is deployed on: solana (default), ethereum, base, robinhood. Required for any 0x address, because the same contract address can exist on several EVM chains. Omit it for Solana. An unsupported value is rejected before any request is spent; EVM chains need a key on an All-Chains plan."

First observedSep 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent and openWorld, and the description adds genuinely non-structured behavior: no pagination, a 15-minute cache that can lag activity figures, a one-API-unit cost, and a defined empty state (empty list plus largestHumanPct) so the agent can interpret a null result.

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 threshold definition, then row contents, then operational caveats, then routing — a sensible order with no filler sentences. The single dense paragraph is long and packs several ideas without visual separation, which slightly hurts scannability.

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 two-parameter read tool with full schema coverage, annotations and an output schema, this covers everything an agent needs: cost, caching, pagination, empty-state semantics, prerequisites (run after get_holders) and sibling routing. No material gap remains.

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%, and the schema itself documents chain semantics, defaults, address formats and rejection behavior in detail. The description only adds 'Arguments: address and chain; one API unit on any chain', which is marginal over the schema, so the baseline 3 applies.

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 verb and resource (whale wallets for a token) and defines the exact inclusion threshold: at least 1% of supply after removing pools, lockers, treasuries and custodial accounts. It also enumerates the row content, distinguishing it precisely from the sibling holder and smart-money tools.

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?

Explicitly positions itself in a workflow ('use it after get_holders when the question is about who can dump') and names three exclusions with the alternative for each: get_holders for the full ranked list, get_smart_money for historically profitable wallets, get_dev_tracker for the creator's wallet.

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

All DeFade — Multi-Chain Memecoin Analyzer 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?