Skip to main content
Glama

intel

by io.chainhelix
OverviewDiscussionsAdmin

whale_flows

Requires a ChainHelix API key as bearer token, or 2 cents per call paid over Binance b402 in USDT, USDC, USD1 or U on BNB Smart Chain, or over x402 in USDC on the Base network. Large transfer counts and USD totals per chain. window in hours default 24 max 168, threshold 500000 USD. Chains covered: every chain except bitcoin

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNo
windowNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaNo
receiptNo
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedOutput schema / properties / results / items / properties / exchangeTouching / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
    • changedOutput schema / properties / results / items / properties / totalUsd / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
    • changedOutput schema / properties / results / items / properties / transfers / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
    • addedOutput schema / properties / results / items / properties / unavailable
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"
  3. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"
  4. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"
  5. Changed2 schema fields changed
    • addedInput schema / x-lexicon
      Added value: +{
+  "bundleSha256": "c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4",
+  "name": "ChainHelix Agentic Lexicon",
+  "resolve": "lexicon_resolve",
+  "spec": "lexicon_spec",
+  "version": "0.1.0"
+}
    • addedInput schema / x-vocab
      Added value: +{
+  "chain": "onchain.chain",
+  "window": "market.window"
+}
  6. Changed1 schema field changed
    • changedInput schema / properties / chain / enum
      Previous value: -[
-  "bitcoin",
-  "ethereum",
-  "bnb",
-  "solana",
-  "avalanche",
-  "xrp",
-  "tron",
-  "polygon",
-  "sui"
-]New value: +[
+  "ethereum",
+  "bnb",
+  "solana",
+  "avalanche",
+  "xrp",
+  "tron",
+  "polygon",
+  "sui"
+]
  7. Changed5 schema fields changed
    • addedOutput schema / properties / meta
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "contentHash": {
+      "type": "string"
+    },
+    "generated": {
+      "type": "number"
+    },
+    "priceUsd": {
+      "type": "number"
+    },
+    "validUntil": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / receipt
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "bytes": {
+      "type": "number"
+    },
+    "covers": {
+      "type": "string"
+    },
+    "issuedAt": {
+      "type": "number"
+    },
+    "lookup": {
+      "type": "string"
+    },
+    "network": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "nonce": {
+      "type": "string"
+    },
+    "seq": {
+      "type": "number"
+    },
+    "settleTx": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sha256": {
+      "type": "string"
+    },
+    "tool": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / results / items / properties / largest
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "t": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "tx": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "valueUsd": {
+        "type": "number"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / results / items / properties / latestAt
      Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
    • addedOutput schema / properties / results / items / properties / source
      Added value: +{
+  "type": "string"
+}
  8. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "items": {
+        "properties": {
+          "chain": {
+            "type": "string"
+          },
+          "exchangeTouching": {
+            "type": "number"
+          },
+          "totalUsd": {
+            "type": "number"
+          },
+          "transfers": {
+            "type": "number"
+          },
+          "windowHours": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}
  9. First observed

TDQS

C2/5.0
Behavior2/5

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

With no annotations provided, the description must carry the full behavioral burden. It discloses authentication/payment requirements and a threshold, but does not describe the response format, whether it is read-only, pagination, rate limits, or any side effects. The mention of '2 cents per call' is useful but the behavior of the tool itself remains unclear.

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

Conciseness2/5

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

The description is a single run-on sentence mixing payment details, data description, parameters, and scope. It is not structured, front-loads payment info instead of the purpose, and includes irrelevant payment specifics that could be omitted or placed later.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with only 2 parameters and existing output schema, the description should clearly state what is returned. It does not describe the output schema or even the nature of the response. It also fails to explain how chain values map to the schema enum, leaving the agent uncertain about valid inputs.

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

Parameters2/5

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

Schema coverage is 0%, so the description must compensate. It partially explains 'window' (default 24, max 168) but says nothing about 'chain' beyond a contradictory claim: 'every chain except bitcoin' while the schema enum lists only 8 specific chains. The threshold is mentioned but is not a parameter, so it adds confusion rather than clarifying the inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description mentions 'Large transfer counts and USD totals per chain' but does not clearly state the tool's action (e.g., 'list', 'return', 'fetch'). It is ambiguous what 'whale_flows' actually does, and it does not distinguish itself from sibling tools like stablecoin_flows or bridge_flows beyond the vague 'whale' concept.

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

Usage Guidelines2/5

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

No guidance on when to use this tool compared to alternatives. It provides parameter defaults (window, threshold) but no contextual advice on selecting this tool over similar flow tools. The description does not mention any exclusions or specific use cases.

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

All intel 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