Skip to main content

intel

by io.chainhelix

Overview Discussions Admin

list_reveals

Read-only

Matured signal reveals, each with its sealed record, salt, hash, opBNB commit transaction, BNB Smart Chain anchor and Merkle path, up to 500 per call; without month, the latest reveals and the list of months. Optional month YYYY-MM and limit

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_reveals"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Number of reveals, whole number 1 to 500, default 100. Example: 50
`month`	No	Calendar month in UTC, YYYY-MM. Example: 2026-10

Output Schema

Name	Required	Description	Default
`month`	No
`latest`	No
`months`	No
`reveals`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 25, 2026

addedInput schema / properties / limit / description

Added value: +"Number of reveals, whole number 1 to 500, default 100. Example: 50"

addedInput schema / properties / month / description

Added value: +"Calendar month in UTC, YYYY-MM. Example: 2026-10"

Changed1 schema field changedOct 16, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"New value: +"25cc80db6d8e9eac73d47a50f7ad6333a21f1972d008a8fed0159de8bfb4b519"

Changed2 schema fields changedOct 16, 2026

changedInput schema / x-lexicon / bundleSha256

Previous value: -"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"New value: +"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"

changedInput schema / x-lexicon / version

Previous value: -"0.1.0"New value: +"0.2.0"

Changed1 schema field changedOct 15, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

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"

Changed3 schema fields changedSep 19, 2026

addedInput schema / x-aliases

Added value: +{
+  "limit": [
+    "Limit",
+    "limits",
+    "$limit",
+    "_limit",
+    "Limits"
+  ],
+  "month": [
+    "months",
+    "Month"
+  ]
+}

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: +{
+  "limit": "data.limit",
+  "month": "data.month"
+}

Changed1 schema field changedAug 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "latest": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "chain": {
+            "type": "string"
+          },
+          "direction": {
+            "type": "string"
+          },
+          "hash": {
+            "type": "string"
+          },
+          "opbnbTx": {
+            "type": "string"
+          },
+          "price": {
+            "type": "number"
+          },
+          "probability": {
+            "type": "number"
+          },
+          "salt": {
+            "type": "string"
+          },
+          "seq": {
+            "type": "number"
+          },
+          "ts": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "month": {
+      "type": "string"
+    },
+    "months": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "reveals": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "chain": {
+            "type": "string"
+          },
+          "direction": {
+            "type": "string"
+          },
+          "hash": {
+            "type": "string"
+          },
+          "opbnbTx": {
+            "type": "string"
+          },
+          "price": {
+            "type": "number"
+          },
+          "probability": {
+            "type": "number"
+          },
+          "salt": {
+            "type": "string"
+          },
+          "seq": {
+            "type": "number"
+          },
+          "ts": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedAug 4, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The readOnlyHint annotation already establishes the safety profile, and the description adds useful behavioral context: the response includes sealed records, salts, hashes, commit/anchor data, and Merkle paths, capped at 500 per call. It also explains the fallback when month is omitted, though it does not discuss auth or rate limits.

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 semicolon-linked sentence is dense but front-loads the purpose and packs in the important return payload and fallback behavior. It is appropriately sized, though the phrasing could be easier to scan if split into two sentences.

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

Completeness4/5

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

With only two optional parameters, full schema coverage, and an output schema, the description provides enough context to invoke the tool correctly. The main missing element is explicit guidance on when to choose this tool over related siblings.

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 coverage is 100%, so limit and month are already well documented. The description still adds meaningful semantics by explaining that omitting month returns the latest reveals plus the list of available months, which is behavior not captured by the schema alone.

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: listing matured signal reveals, and it enumerates the payload each reveal contains. It is clearly not a verification or single-reveal tool, though it does not explicitly name sibling tools such as verify_reveal to sharpen the distinction.

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?

The description explains the effect of omitting month, but it does not say when an agent should use this tool versus alternatives like verify_reveal or latest_signals. There are no explicit exclusions or alternative-routing instructions.

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

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?