Skip to main content
Glama

Crypto Data & Market Analysis Agent

by app.vercel.asistent-crypto
OverviewDiscussionsAdmin

get_eth_whale_flows

Read-onlyIdempotent

Large ETH transfers (>100 ETH) to and from live exchange hot wallets (Binance, Coinbase, Bitfinex) in the last 2 hours. Inflows to exchanges suggest potential selling pressure, outflows suggest accumulation. Call for smart-money signals and exchange flows. Wallets that could not be read are listed under "unavailable" rather than dropped, so an empty result is never mistaken for a quiet market. The response also states how far back each wallet could actually be read: the busiest exchange wallets produce thousands of transfers an hour, and a tool that silently sees only the last few minutes of one reports calm that was never measured.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
flowsYesLarge ETH transfers to and from known exchange wallets, largest first.
coverageYesHow much of that window each wallet could actually be read back over. A busy wallet can exhaust one page before reaching the far end.
unavailableYesExchange wallets that could not be read. An empty flows list with entries here means nothing was read, not that nothing moved.
windowMinutesYesThe window asked for, in minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedOutput schema / properties / coverage
      Added value: +{
+  "description": "How much of that window each wallet could actually be read back over. A busy wallet can exhaust one page before reaching the far end.",
+  "items": {
+    "properties": {
+      "exchange": {
+        "type": "string"
+      },
+      "minutesCovered": {
+        "type": "number"
+      },
+      "truncated": {
+        "description": "true means the wallet is too busy for a single page, so older transfers in the window were not seen.",
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "exchange",
+      "minutesCovered",
+      "truncated"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / flows
      Added value: +{
+  "description": "Large ETH transfers to and from known exchange wallets, largest first.",
+  "items": {
+    "properties": {
+      "counterparty": {
+        "description": "The non-exchange side of the transfer.",
+        "type": "string"
+      },
+      "direction": {
+        "description": "`in` is flow toward the exchange (distribution pressure), `out` is away.",
+        "enum": [
+          "in",
+          "out"
+        ],
+        "type": "string"
+      },
+      "exchange": {
+        "type": "string"
+      },
+      "hash": {
+        "type": "string"
+      },
+      "timestamp": {
+        "description": "Unix seconds.",
+        "type": "number"
+      },
+      "valueEth": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "exchange",
+      "valueEth",
+      "direction",
+      "timestamp",
+      "hash"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "description": "Large ETH transfers to and from known exchange wallets, newest first.",
-  "items": {
-    "properties": {
-      "counterparty": {
-        "description": "The non-exchange side of the transfer.",
-        "type": "string"
-      },
-      "direction": {
-        "description": "`in` is flow toward the exchange (distribution pressure), `out` is away.",
-        "enum": [
-          "in",
-          "out"
-        ],
-        "type": "string"
-      },
-      "exchange": {
-        "type": "string"
-      },
-      "hash": {
-        "type": "string"
-      },
-      "timestamp": {
-        "description": "Unix seconds.",
-        "type": "number"
-      },
-      "valueEth": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "exchange",
-      "valueEth",
-      "direction",
-      "timestamp",
-      "hash"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
    • addedOutput schema / properties / unavailable
      Added value: +{
+  "description": "Exchange wallets that could not be read. An empty flows list with entries here means nothing was read, not that nothing moved.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / windowMinutes
      Added value: +{
+  "description": "The window asked for, in minutes.",
+  "type": "number"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "flows",
+  "windowMinutes",
+  "coverage",
+  "unavailable"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "description": "Large ETH transfers to and from known exchange wallets, newest first.",
+      "items": {
+        "properties": {
+          "counterparty": {
+            "description": "The non-exchange side of the transfer.",
+            "type": "string"
+          },
+          "direction": {
+            "description": "`in` is flow toward the exchange (distribution pressure), `out` is away.",
+            "enum": [
+              "in",
+              "out"
+            ],
+            "type": "string"
+          },
+          "exchange": {
+            "type": "string"
+          },
+          "hash": {
+            "type": "string"
+          },
+          "timestamp": {
+            "description": "Unix seconds.",
+            "type": "number"
+          },
+          "valueEth": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "exchange",
+          "valueEth",
+          "direction",
+          "timestamp",
+          "hash"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description reveals crucial behavioral details: the threshold for transfers, the interpretation of inflows/outflows, the 'unavailable' wallet handling to avoid false empty results, and the honest disclosure of read-depth limitations. This goes far beyond 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?

The description is concise yet rich, with every sentence adding value. It is front-loaded with the core function, followed by interpretation guidance, and a critical caveat about data coverage. No word is wasted, and the structure supports quick comprehension.

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 zero-parameter tool, the description covers the data scope, interpretation, edge cases, and measurement limitations. The output schema exists but need not be repeated. It is complete and self-sufficient for an agent to select and invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the baseline is 4. The description adds meaningful context about the data returned and its interpretation, but since there are no parameters to explain, this score is appropriate.

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?

The description clearly states a specific verb and resource: it reports large ETH transfers (>100 ETH) to and from exchange hot wallets. It distinguishes itself from sibling tools by specifying the ETH exchange flow focus and the 2-hour window, making its unique purpose unmistakable.

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?

The description explicitly says 'Call for smart-money signals and exchange flows,' providing a direct usage context. It does not name alternatives or state when not to use, but the clear purpose and context are sufficient for guiding an agent.

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

All Crypto Data & Market Analysis Agent 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