Skip to main content
Glama

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, one row per transaction over 500,000 USD, with exchangeTouching = transfers from or to a known exchange hot wallet or deposit address. What is counted: ethereum, bnb, polygon, avalanche native-coin transfers (token transfers such as USDT and USDC are not included); tron TRX and TRC-20 stablecoins; xrp native XRP; sui native SUI; bitcoin since 2026-09-25, the value sent to addresses other than the sender. exchangeTouching is null on bitcoin, tron and sui (too few labelled exchange addresses). Large solana transfers are not captured: the solana row answers null. window in hours default 24 max 168

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNo
windowNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaNo
receiptNo
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "ethereum",
      -  "bnb",
      -  "solana",
      -  "avalanche",
      -  "xrp",
      -  "tron",
      -  "polygon",
      -  "sui"
      -]New value: +[
      +  "bitcoin",
      +  "ethereum",
      +  "bnb",
      +  "solana",
      +  "avalanche",
      +  "xrp",
      +  "tron",
      +  "polygon",
      +  "sui"
      +]
  2. 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"
      +  ]
      +}
  3. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"
  4. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"
  5. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"
  6. 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"
      +}
  7. 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"
      +]
  8. 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"
      +}
  9. 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"
      +}
  10. First observed

TDQS

A3.7/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 so well: it discloses auth/payment requirements (API key or 2 cents via Binance b402/x402), that exchangeTouching is null on bitcoin/tron/sui, that the solana row returns null, and the window bounds (default 24, max 168). It stops short of describing pagination, rate limits, or output shape, but the coverage/null semantics are unusually explicit.

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?

It is one dense run-on paragraph with no structural breaks, and the most important content (what the tool measures) is preceded by payment/auth logistics. Almost every sentence carries information, but the front-loading is poor and the readability suffers for a definition of this length.

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 spelled out, and the description covers the operationally critical unknowns: cost, coverage gaps, null semantics, and window bounds. What remains missing is guidance on choosing this tool versus bridge_flows/stablecoin_flows/victim_flow for adjacent flow questions.

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?

Schema description coverage is 0%, so the description must compensate, and it largely does: window is defined in hours with a default of 24 and a hard max of 168, and the chain parameter's semantics are expanded via a per-chain enumeration of what is counted and which chains return null for exchangeTouching. The distinction between native-coin and token transfers per chain is meaningful added semantics.

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?

States a concrete verb+resource: large transfer counts and USD totals per chain, one row per transaction over 500,000 USD. It implicitly separates itself from siblings like stablecoin_flows by explicitly excluding token transfers such as USDT/USDC, though it never names the alternative directly. The core purpose is buried after the payment preamble but is recoverable.

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?

Usage context is implied by the $500k threshold and the listed coverage per chain, and the exclusions (solana not captured, stablecoins excluded) implicitly steer the agent toward other tools. However, there is no explicit when-to-use/when-not-to-use statement and no sibling is named as an alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources