intel

market_state

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. Regime, range age, volatility state and momentum per chain: RSI 14 on 1h, 4h and 1d, MACD 12/26/9 on 1h and 4h, the 4h EMA trend and one summary momentum state. Omit chain for all nine

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chain`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	No
`receipt`	No
`results`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 22, 2026
- changedOutput schema / properties / results / items / properties / lastPrice / type
```
Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
```

Changed1 schema field changedSep 21, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"

Changed1 schema field changedSep 19, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"

Changed1 schema field changedSep 19, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"

Changed2 schema fields changedSep 19, 2026

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"
+}

Changed5 schema fields changedSep 5, 2026

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 / asOf
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
addedOutput schema / properties / results / items / properties / regimeAsOf
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
addedOutput schema / properties / results / items / properties / source
```
Added value: +{
+  "type": "string"
+}
```

Changed1 schema field changedAug 24, 2026

addedOutput schema / properties / results / items / properties / momentum

Added value: +{
+  "additionalProperties": true,
+  "properties": {
+    "macd": {
+      "properties": {
+        "h1": {
+          "additionalProperties": true,
+          "type": [
+            "object",
+            "null"
+          ]
+        },
+        "h4": {
+          "additionalProperties": true,
+          "type": [
+            "object",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "rsi14": {
+      "properties": {
+        "d1": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "h1": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "h4": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "state": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "trend4h": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed3 schema fields changedAug 12, 2026
- removedOutput schema / properties / results / items / properties / range5dPct
```
Removed value: -{
-  "type": [
-    "number",
-    "null"
-  ]
-}
```
- addedOutput schema / properties / results / items / properties / regime
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / results / items / properties / regimeAgeHours
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```

Changed1 schema field changedAug 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "items": {
+        "properties": {
+          "chain": {
+            "type": "string"
+          },
+          "lastPrice": {
+            "type": "number"
+          },
+          "range14dPct": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "range5dPct": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "volRatio24hVs14d": {
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results"
+  ],
+  "type": "object"
+}

First observedAug 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses payment requirements (API key or per-call cost) and the default behavior of returning all chains when omitted, which is useful. However, it does not mention rate limits, error handling, or whether the operation is read-only (though it implies a read). The absence of any note on response structure is partially mitigated by the existence of an output schema, but other behavioral traits remain undisclosed.

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 description is a single dense sentence that mixes payment details, indicator specifications, and parameter behavior. While information-dense, it lacks clear structure and could be broken into separate clauses or bullet points. The payment method details are lengthy and could be moved to annotations or a separate field, making the description less concise but not excessively verbose.

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?

For a tool with a single optional parameter and an output schema, the description covers the core behavior (what indicators are returned and the chain scope). However, it does not mention any prerequisites beyond payment, nor does it describe error scenarios or auth flows in detail. The lack of usage guidance and behavioral constraints leaves gaps, but the presence of an output schema reduces the need to explain return format. Overall, it is adequate but not fully complete.

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?

The schema provides only an enum for 'chain' with no description of its meaning or optionality. The description adds substantial value by explaining that the tool operates 'per chain' and that omitting the chain returns all nine chains. This clarifies the parameter's purpose and default behavior beyond what the schema alone offers.

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 enumerates the specific indicators (RSI, MACD, EMA, momentum state) and states they are provided per chain, with the option to return all nine chains when the chain parameter is omitted. This clearly defines the tool's function and distinguishes it from other market data tools like 'candles' or 'prices' by its unique set of technical indicators.

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?

There is no explicit guidance on when to use this tool versus alternatives. Only parameter behavior is mentioned ('Omit chain for all nine'), but no context on when this tool is preferred over sibling tools like 'candles', 'instrument_signals', or 'chain_brief'. No exclusions or alternative selection criteria are provided, leaving the agent to infer usage from the tool name.

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

All intel tools Inspect

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

Need Help?