Skip to main content
Glama

intel

by io.chainhelix
OverviewDiscussionsAdmin

deep_report

Requires a ChainHelix API key as bearer token, or 25 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. The complete nine chain research brief in one call: the full market report with price walls, large transfers and bot activity, the live signal stream with conviction scores and ranking tiers, cross chain correlations, options volatility, session statistics and the proof stream counters, with links to verify every signal on chain. The most complete single answer this server produces

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
metaNo
proofNo
reportNo
verifyNo
receiptNo
signalsNo
sessionsNo
generatedYes
correlationsNo
optionsVolatilityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"
  2. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"
  3. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"
  4. 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"
+}
  5. Changed4 schema fields changed
    • removedOutput schema / properties / optionsVolatility / additionalProperties
      Removed value: -true
    • changedOutput schema / properties / optionsVolatility / type
      Previous value: -[
-  "object",
-  "null"
-]New value: +[
+  "array",
+  "object",
+  "null"
+]
    • removedOutput schema / properties / sessions / additionalProperties
      Removed value: -true
    • changedOutput schema / properties / sessions / type
      Previous value: -[
-  "object",
-  "null"
-]New value: +[
+  "array",
+  "object",
+  "null"
+]
  6. Changed2 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"
+}
  7. Added

TDQS

A3.5/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 burden. It discloses authentication/payment requirements upfront and mentions the inclusion of verification links ('links to verify every signal on chain'). It does not discuss side effects or read-only nature explicitly, but as a report tool, it's reasonable to infer safety. The disclosure of access prerequisites is valuable.

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 dense wall of text, with the payment requirement taking the entire first sentence—secondary to the actual purpose. The second sentence enumerates many components without clear structure or front-loading of the core action. It is overwritten and could be split into a clear purpose statement followed by usage details.

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

Completeness3/5

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

The description covers the tool's output contents in detail and mentions access requirements, but it omits any explanation of the `chain` parameter, which is a core input. While the output schema exists to document return values, the input semantics remain ambiguous. The tool's complexity (nine chains, many components) could benefit from more explicit usage guidance and clarification of the parameter's role.

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?

The description does not mention the `chain` parameter at all, despite the schema having a single enum parameter with 0% description coverage. The agent is left unaware whether to pass a chain, what it controls, or if it is optional. The description focuses on the overall output but fails to explain how the parameter affects the result, leaving a critical gap in usage understanding.

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 explicitly states the tool's purpose: 'The complete nine chain research brief in one call' and enumerates the components (market report, signal stream, correlations, volatility, etc.). It distinguishes itself from siblings by claiming 'The most complete single answer this server produces,' making the resource and scope unambiguous.

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 provides clear context on payment/auth requirements ('Requires a ChainHelix API key as bearer token, or 25 cents per call...') but does not explicitly direct when to use this tool versus alternatives. It implies comprehensiveness ('most complete') but does not name sibling tools or state when not to use it. No explicit routing or exclusions are given.

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