DropEngine x402 Agent Services

analyze_whale_activity

Paid Whale Intelligence ($0.02 USDC). Summarizes large public GeckoTerminal-indexed DEX trades for a token address on a supported chain. Large-trader labels are size-based heuristics, not verified whale identities; data is not chain-wide. Wallet mode uses Helius (Solana) or Etherscan API V2 (EVM) when configured, returning recent indexed transactions only; it does not claim complete balances or whale labels.

Agent entry points: risky external action → use Agent Action Gate when a combined action-specific safety assessment is needed; unclear capability/provider → use free /api/discover; constrained comparison between callable alternatives → use paid route_tool; known single capability → call the direct tool; multi-step objective → read the matching workflow recipe and call only relevant steps. Workflows are stateless recipes, not executors; calls are paid separately and are not bundle charged. Agent Action Gate does not approve payment, sign or broadcast transactions, evaluate seller reputation, replace transaction simulation, replace route_tool, or replace human approval.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`meta`	No
`next`	No
`tool`	Yes
`error`	No
`result`	No
`status`	No
`payment`	No
`success`	Yes
`agent_ux`	No
`timestamp`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 8, 2026

addedOutput schema / properties / agent_ux

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "error": {
+      "anyOf": [
+        {},
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "meta": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "next": {
+      "items": {},
+      "type": "array"
+    },
+    "payment": {
+      "additionalProperties": false,
+      "properties": {
+        "execution_status": {
+          "enum": [
+            "not_started",
+            "succeeded",
+            "failed",
+            "unknown"
+          ],
+          "type": "string"
+        },
+        "status": {
+          "enum": [
+            "not_required",
+            "required",
+            "settled",
+            "failed",
+            "unknown"
+          ],
+          "type": "string"
+        }
+      },
+      "required": [
+        "status",
+        "execution_status"
+      ],
+      "type": "object"
+    },
+    "result": {},
+    "status": {
+      "enum": [
+        "succeeded",
+        "failed",
+        "partial",
+        "outcome_unknown"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "result",
+    "error",
+    "meta",
+    "payment",
+    "next"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / error

Added value: +{
+  "anyOf": [
+    {},
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / meta / additionalProperties
```
Previous value: -falseNew value: +{}
```

removedOutput schema / properties / meta / properties

Removed value: -{
-  "cache": {
-    "additionalProperties": false,
-    "properties": {
-      "age_ms": {
-        "minimum": 0,
-        "type": "number"
-      },
-      "hit": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "hit",
-      "age_ms"
-    ],
-    "type": "object"
-  },
-  "failed_sources": {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "reason": {
-          "type": "string"
-        },
-        "source": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "source",
-        "reason"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "latency_ms": {
-    "minimum": 0,
-    "type": "number"
-  },
-  "partial": {
-    "type": "boolean"
-  },
-  "sources": {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  }
-}

addedOutput schema / properties / meta / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / meta / required

Removed value: -[
-  "sources",
-  "latency_ms",
-  "partial",
-  "failed_sources",
-  "cache"
-]

addedOutput schema / properties / next

Added value: +{
+  "items": {},
+  "type": "array"
+}

addedOutput schema / properties / payment

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "execution_status": {
+      "enum": [
+        "not_started",
+        "succeeded",
+        "failed",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "not_required",
+        "required",
+        "settled",
+        "failed",
+        "unknown"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "execution_status"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / result
```
Added value: +{}
```

addedOutput schema / properties / status

Added value: +{
+  "enum": [
+    "succeeded",
+    "failed",
+    "partial",
+    "outcome_unknown"
+  ],
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "success",
-  "tool",
-  "timestamp",
-  "data",
-  "meta"
-]New value: +[
+  "success",
+  "tool",
+  "timestamp",
+  "data"
+]

First observedSep 28, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the paid cost ($0.02 USDC), the data source (GeckoTerminal-indexed DEX trades), the wallet-mode backends (Helius for Solana, Etherscan API V2 for EVM), and candid limitations (labels are size heuristics, data is not chain-wide, no complete balances). It stops short of describing rate limits, pagination, or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The tool-specific opening is well front-loaded (paid flag and purpose first), but the lengthy 'Agent entry points' block is suite-wide boilerplate that does not earn its place in this tool's description and dilutes focus. The core content is buried under routing meta-guidance.

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?

An output schema exists, so return values need not be described, and the two modes are explained. Combined with the candid data-source and limitation disclosures, an agent has enough to invoke it correctly; only parameter-level detail (window/min_transaction_usd semantics) is left to the schema.

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 the mode/asset/chain/limit/window/min_transaction_usd/address fields, establishing the baseline of 3. The description clarifies the semantic difference between asset mode (token address) and wallet mode (recent indexed transactions), but adds no meaning for limit, window, or min_transaction_usd thresholds.

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?

The opening states a specific verb+resource ('Summarizes large public GeckoTerminal-indexed DEX trades') and scope ('for a token address on a supported chain'), and distinguishes two operating modes (asset vs wallet). It is clear what the tool does, though differentiation from siblings relies on generic routing boilerplate rather than tool-specific comparison.

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?

The 'Agent entry points' block gives routing rules (unclear capability → /api/discover; comparison → route_tool; known single capability → direct tool), but this guidance is generic across the whole suite, not tailored to when whale-activity analysis is the right choice. There is no explicit when-not-to-use condition specific to this tool.

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

All DropEngine x402 Agent Services 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?