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: -"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 burden of disclosing behavior. It clearly explains what the digest contains and where it is stored, which helps set expectations. However, it does not mention whether the operation is read-only, any rate limits, failure behavior for invalid or missing dates, or other execution traits.
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?
Two sentences with no filler. The core purpose is front-loaded, and the parameter behavior is stated in a compact second sentence. Every clause earns its place.
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?
Given a single optional parameter and an existing output schema, the description covers the essential semantics: what the digest aggregates, where it is stored, and how the date parameter behaves. It could add clarification about default 'latest' resolution or error behavior, but it is largely complete for calling this tool correctly.
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?
The schema provides only a bare string property with 0% description coverage, so the description must compensate. It does: 'Optional date YYYY-MM-DD, default the latest' specifies the format, optionality, and default behavior. It stops short of explaining timezone handling or valid date ranges, but this is solid compensation for one parameter.
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 names a highly specific resource: the per-day Merkle digest of reveals, hire deliverables, and verification records on BNB Greenfield, sealed on opBNB. The purpose is unmistakable, though it lacks an explicit verb like 'fetch' or 'list' and does not directly differentiate itself from sibling tools.
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 guidance on when to prefer this tool over alternatives such as list_reveals, attestation_stats, or data_changelog. The only contextual hint is the parameter default ('default the latest'), which addresses invocation behavior, not tool selection.
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.