Skip to main content
Glama

intel

by io.chainhelix
OverviewDiscussionsAdmin

mev_intel

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. MEV event rates per chain and type vs the trailing weekly pace. window in hours, default 24, max 168. Types overlap and must not be summed: a backrun transaction also emits an arbitrage row. NFT coverage is ERC-721 only, so nft_mev excludes all ERC-1155 activity. 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. Changed4 schema fields changed
    • changedOutput schema / properties / results / items / properties / count / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
    • changedOutput schema / properties / results / items / properties / type / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • addedOutput schema / properties / results / items / properties / unavailable
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedOutput schema / properties / results / items / properties / weeklyPaceSameWindow / type
      Previous value: -"number"New value: +[
+  "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. Changed6 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 / calibration
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / results / items / properties / latestBucket
      Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
    • addedOutput schema / properties / results / items / properties / rule
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "changedInsideWindow": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "rule": {
+      "type": "string"
+    },
+    "since": {
+      "type": "string"
+    }
+  },
+  "type": [
+    "object",
+    "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"
+          },
+          "count": {
+            "type": "number"
+          },
+          "type": {
+            "type": "string"
+          },
+          "weeklyPaceSameWindow": {
+            "type": "number"
+          },
+          "windowHours": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}
  9. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral disclosure burden, and it does so well. It reveals critical operational traits: required bearer-token or per-call payment via specific channels, the warning that event types overlap and must not be summed, the ERC-721-only NFT coverage limitation, and the exact chain set. This is substantial context beyond the basic function.

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?

Every clause carries useful information with no filler, but the structure is a single dense run-on paragraph. Payment details are front-loaded ahead of the actual purpose, which forces an agent to parse through commercial terms before learning what the tool reports. The information density earns a pass, yet the ordering and lack of sentence breaks hurt skimmability.

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 two-parameter query tool with an output schema present, this description is remarkably complete. It covers parameter semantics, supported chains, a critical data-shape caveat (overlapping types), coverage limits (ERC-721 only), and the unusual payment requirement an agent must satisfy before invoking. The output schema handles return-value documentation, so nothing an agent needs to call 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 largely does. It specifies window units (hours), default (24), and maximum (168), and enumerates valid chain values. This adds real meaning beyond the bare schema types. Minor gap: the description mentions 'type' as a dimension but the schema has no type parameter, leaving ambiguity about whether type is an input or output facet.

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 conveys a specific function: reporting MEV event rates per chain and type compared against the trailing weekly pace. This is clear enough for an agent to grasp the resource and metric. However, it does not explicitly differentiate from sibling MEV tools (mev_pressure, mev_bots, mev_flow_spec), and the purpose is phrased as a noun fragment rather than a verb-led statement.

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 is given on when to choose this tool over its MEV-related siblings (mev_pressure, mev_bots, mev_flow_spec). The description provides parameter constraints (window bounds, chain list) but never states the condition that selects this tool versus alternatives. An agent is left to infer appropriateness from the metric name.

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