Skip to main content
Glama

intel

by io.chainhelix
OverviewDiscussionsAdmin

liquidations

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. Lending liquidations per chain, protocol and direction over a window: event count, distinct borrowers and liquidators, and per token the amount liquidated (debt covered and collateral seized) with its USD value where the price is certain (USD stablecoins at $1, wrapped ETH, BTC, BNB, AVAX and POL at the latest hourly close; other tokens amount only, counted in unpricedLegs). Compound v2 and Venus events carry no token addresses and give counts only. window in hours, default 24, max 720; each hour is published about 90 minutes after it ends. Omit chain for all Chains covered: ethereum, bnb, avalanche, polygon.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNo
windowNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaNo
receiptNo
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / properties / results / items / properties / collateralUsd
      Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
    • addedOutput schema / properties / results / items / properties / debtUsd
      Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
    • addedOutput schema / properties / results / items / properties / latestAt
      Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
    • addedOutput schema / properties / results / items / properties / tokens
      Added value: +{
+  "type": "array"
+}
    • addedOutput schema / properties / results / items / properties / unpricedLegs
      Added value: +{
+  "type": [
+    "number",
+    "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",
+  "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 / latestBucket
      Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
    • addedOutput schema / properties / results / items / properties / source
      Added value: +{
+  "type": "string"
+}
  8. Added

TDQS

A4.4/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/payment requirements (bearer key or 2 cents via b402/x402), publication latency (~90 minutes after each hour ends), pricing coverage limits (only certain tokens priced; others counted in unpricedLegs), and a data caveat that Compound v2 and Venus events carry no token addresses and return counts only.

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

Conciseness4/5

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

The single dense paragraph contains almost no filler; every clause (payment, pricing caveat, window rule, chain omission) carries operational weight. However, it front-loads payment mechanics instead of the purpose, pushing the actual 'what it does' statement to the second sentence, which is a minor structural weakness.

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?

Despite zero annotations, the description covers auth, latency, data limitations, valuation caveats, and both parameters, and an output schema exists so return values need not be re-explained. Nothing an agent needs to call this tool correctly is missing.

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 does: window is defined as hours with default 24 and max 720, and chain's omission semantics ('omit chain for all chains covered') plus the covered chain list are stated. This substantially exceeds what the bare enum/type schema conveys.

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 gives a specific resource and verb: lending liquidations per chain, protocol and direction over a window, returning event counts, distinct borrowers/liquidators, and per-token amounts liquidated with USD valuation. This is clearly distinguishable from siblings like whale_flows, stablecoin_flows or mev_intel, which concern different phenomena.

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?

It explains how to scope the call (omit chain for all covered chains, window default 24 / max 720) and the freshness rule, but never states when to choose this tool over an alternative sibling such as mev_intel or whale_flows. Usage is implied by the data description rather than explicitly routed.

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