Skip to main content
Glama

intel

by io.chainhelix
OverviewDiscussionsAdmin

stablecoin_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. Stablecoin mints and burns of 10,000 USD or more per chain and coin over a window: counts, total dollars, large events, and the net of mints minus burns. Coins recorded since 2026-09-30T03:30Z: ethereum USDT, USDC, USD1, USDS; bnb USDT, USDC, USD1, U; polygon USDT, USDC, USDC.e; avalanche USDT, USDC; solana USDC, USDT; tron USDT. Every recorded coin is answered, with zeros when it had no mint or burn in the window. DAI and PYUSD are not recorded after 2026-09-30T03:30Z. window in hours, default 24, max 720. Omit chain for all six chains

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",
-  "avalanche",
-  "polygon"
-]New value: +[
+  "ethereum",
+  "bnb",
+  "polygon",
+  "avalanche",
+  "solana",
+  "tron"
+]
  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",
+  "avalanche",
+  "polygon"
+]
  7. Changed4 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 / latestAt
      Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
    • addedOutput schema / properties / results / items / properties / source
      Added value: +{
+  "type": "string"
+}
  8. Added

TDQS

A4.2/5.0
Behavior5/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 requirements (ChainHelix API key bearer token) and two paid paths (Binance b402 in USDT/USDC/USD1/U on BNB Smart Chain, or x402 USDC on Base). It also discloses coverage caveats (DAI and PYUSD not recorded after 2026-09-30T03:30Z, coin support per chain) and return semantics (every recorded coin answered with zeros when inactive).

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 content is dense and largely earns its place, but it is a single run-on block with the lengthy payment/access prerequisite front-loaded ahead of the actual tool purpose. Splitting access requirements from data semantics would improve front-loading.

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?

An output schema exists, so return-shape explanation is unnecessary. Given zero annotations and two parameters at 0% schema coverage, the description supplies everything needed: access/payment prerequisites, per-chain coin coverage, recording cutoffs, window bounds, and chain omission semantics.

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

Parameters5/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 does: window is documented as hours with default 24 and max 720, and chain's omission behavior ('all six chains') is explained, with the enum values listed in the tokenized chain list. That is effectively complete parameter documentation.

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 description states a specific verb and resource: stablecoin mints and burns per chain and coin over a window, returning counts, total dollars, large events, and mints-minus-burns. That is enough to distinguish it from sibling flow tools like bridge_flows or whale_flows. The opening payment/access sentence delays the actual purpose, and sibling differentiation is implicit rather than stated.

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 description gives concrete operating guidance: window in hours (default 24, max 720), and 'Omit chain for all six chains', plus which coins are recorded per chain. However, it never says when to choose this tool over alternatives like bridge_flows or whale_flows, so usage routing is left to inference.

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