One hash per day: the Merkle digest of every reveal, hire deliverable and verification record stored on BNB Greenfield that day, with its root sealed on opBNB. Optional date YYYY-MM-DD, default the latest
| Name | Required | Description | Default |
|---|---|---|---|
| date | No |
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | ||
| days | No | ||
| root | No | ||
| found | Yes | ||
| leaves | No | ||
| sealed | No | ||
| verify | No | ||
| digestUrl | No | ||
| digestBytes | No | ||
| digestSha256 | No |
Changes observed during successful MCP inspections.
Input schema / x-lexicon / bundleSha256Previous value: -"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"New value: +"25cc80db6d8e9eac73d47a50f7ad6333a21f1972d008a8fed0159de8bfb4b519"Input schema / x-lexicon / bundleSha256Previous value: -"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"New value: +"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"Input schema / x-lexicon / versionPrevious value: -"0.1.0"New value: +"0.2.0"Input schema / additionalPropertiesAdded value: +falseInput schema / x-lexicon / bundleSha256Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"Input schema / x-lexicon / bundleSha256Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"Input schema / x-lexicon / bundleSha256Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"Input schema / x-aliasesAdded value: +{
+ "date": [
+ "Date"
+ ]
+}Input schema / x-lexiconAdded value: +{
+ "bundleSha256": "c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4",
+ "name": "ChainHelix Agentic Lexicon",
+ "resolve": "lexicon_resolve",
+ "spec": "lexicon_spec",
+ "version": "0.1.0"
+}Input schema / x-vocabAdded value: +{
+ "date": "data.date"
+}Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "properties": {
+ "date": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "days": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "digestBytes": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "digestSha256": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "digestUrl": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "found": {
+ "type": "boolean"
+ },
+ "leaves": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "root": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "sealed": {
+ "additionalProperties": true,
+ "type": [
+ "object",
+ "null"
+ ]
+ },
+ "verify": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "found"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It earns credit for disclosing data provenance (BNB Greenfield storage) and the sealing mechanism (opBNB root), which is real context beyond structure. It does not cover whether the digest changes over time, behavior on days with no activity, auth requirements, 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single compact passage that front-loads what the digest is and follows with the parameter contract. No filler sentences, nothing repeated from the schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return-value shape need not be restated. For a single-parameter read tool with no annotations, the description covers purpose, provenance, parameter format, and default, leaving only minor gaps such as empty-day behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% — the schema only declares date as a string. The description compensates by giving the accepted format (YYYY-MM-DD), noting the parameter is optional, and specifying the default (the latest day), which is meaningful guidance beyond the raw schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a concrete artifact — a daily Merkle digest over reveals, hire deliverables, and verification records, with the root sealed on opBNB — which is semantically distinct from siblings like list_reveals or attestation_stats. It is highly specific about the resource, though it is phrased as a noun clause rather than a verb+resource action, so an agent must infer the retrieval operation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no statement of when to use this tool versus alternatives (e.g., list_reveals, verified_delivery, attestation_stats, chain_brief). The only operational hint is the default-date behavior, which is parameter semantics rather than usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.