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
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| month | No |
| Name | Required | Description | Default |
|---|---|---|---|
| month | No | ||
| latest | No | ||
| months | No | ||
| reveals | 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: +{
+ "limit": [
+ "Limit",
+ "limits",
+ "$limit",
+ "_limit",
+ "Limits"
+ ],
+ "month": [
+ "months",
+ "Month"
+ ]
+}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: +{
+ "limit": "data.limit",
+ "month": "data.month"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It does disclose the default branch (month omitted returns latest reveals plus the month list) and the 500-per-call cap, which is meaningful behavioral context. It omits auth/permission requirements, ordering of results, and pagination behavior across the cap.
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?
The resource and payload are front-loaded effectively, but the description is a single dense run-on clause packed with commas. It is informative yet not cleanly structured into separable claims, which taxes quick scanning.
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 explanation is not strictly required, yet the description still enumerates the record contents usefully. Combined with the disclosed default behavior, it is nearly complete for a two-param list tool; only permission and pagination details are missing.
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%, so the two params are undocumented in the schema. The description partially compensates by giving month's format (YYYY-MM) and implying the limit ceiling with 'up to 500 per call', but it does not explain limit's default or range, so a semantic gap remains.
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 specific resource — 'matured signal reveals' — and enumerates the substantial payload each record carries (sealed record, salt, hash, opBNB commit tx, BNB anchor, Merkle path). This is far more specific than the bare name, though it never explicitly contrasts with siblings like verify_reveal.
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?
It states the default behavior when month is omitted ('the latest reveals and the list of months'), which is useful operational context. However, it gives no when-to-use vs alternatives guidance and does not mention verify_reveal or list_attestations, leaving the agent to infer the boundary.
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.