Skip to main content
Glama
Sign In

ChainHelix for Machines

by io.chainhelix.mcp
OverviewDiscussionsAdmin

verify_lead_alert

Read-only

Check one lead alert by seq: its commit status and opBNB transaction, and whether it folds into its anchor. Pass the alert you hold (the row from lead_alerts or from a push, with its salt) as alert and the answer says whether its hash recomputes to the sealed one

Input Schema

NameRequiredDescriptionDefault
seqYesSequence number in the CHXL stream, whole number. Example: 7
alertNoOne alert object exactly as received, with ts, chain, read, direction, hour, price, values and salt. Example: {"ts": 1761350700000, "chain": "bnb", "read": "vol_spike_long", "direction": "long", "hour": 1761346800000, "price": 612.4, "values": {"volumeRatio": 3.1, "macdHist": 0.42}, "salt": "5f2c9a0e1b7d4c3a8e6f0b1d2c3e4f5a"}

Output Schema

NameRequiredDescriptionDefault
seqNo
foundNo
statusNo
opbnbTxNo
revealedNo
hashRecomputesNo
anchorRootRecomputesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / alert / description
      Added value: +"One alert object exactly as received, with ts, chain, read, direction, hour, price, values and salt. Example: {\"ts\": 1761350700000, \"chain\": \"bnb\", \"read\": \"vol_spike_long\", \"direction\": \"long\", \"hour\": 1761346800000, \"price\": 612.4, \"values\": {\"volumeRatio\": 3.1, \"macdHist\": 0.42}, \"salt\": \"5f2c9a0e1b7d4c3a8e6f0b1d2c3e4f5a\"}"
    • addedInput schema / properties / seq / description
      Added value: +"Sequence number in the CHXL stream, whole number. Example: 7"
  2. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"670f7504e3de5031beccee25a2d24e4515f68b893295f6d5b0d3a0665498b2c9"New value: +"25cc80db6d8e9eac73d47a50f7ad6333a21f1972d008a8fed0159de8bfb4b519"
  3. Changed2 schema fields changed
    • 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"
  4. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  5. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"New value: +"e5b4290024a229f2bdf97f8fc6a0079c3fe13b77267f41fdcffeb8b26aa1c41e"
  6. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"New value: +"a1c2e10fd3177d6b4d59ca78693e8fb36880165cf0f735f680dd86a510411178"
  7. Changed1 schema field changed
    • changedInput schema / x-lexicon / bundleSha256
      Previous value: -"c014292cad7497ce9fd68c33345ac32cb42b672c8e77d6c749c26e162cc207e4"New value: +"1eeb782ee15fe69fc80776948e0556fa6b795e210e6305935b2c97b73d955cda"
  8. Changed2 schema fields changed
    • 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: +{
+  "alert": "agent.alert",
+  "seq": "agent.seq"
+}
  9. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the readOnlyHint, the description discloses the verification behavior: it checks commit status, opBNB transaction, anchor folding, and whether the hash recomputes to the sealed one. It does not discuss permissions, rate limits, or mismatch consequences, but adds useful behavioral context for a read-only verification tool.

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?

Two sentences, front-loaded with the core purpose and then the input/result relationship. It is efficient with little waste, though some content overlaps with the schema descriptions.

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 an output schema present and read-only annotations covering safety, the description provides enough context to invoke it correctly: the alert source, required salt, and the verification criterion. It could be richer about commit status or mismatch outcomes, but the essentials are covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with detailed parameter descriptions and examples already present. The description restates that seq selects the alert and that alert is the held row with salt, but adds no syntax or format detail beyond the schema, so baseline 3 is appropriate.

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?

States a specific verb and resource ('Check one lead alert by seq') and enumerates the concrete checks: commit status, opBNB transaction, anchor folding, and hash recomputation. This clearly distinguishes it from the sibling lead_alerts list tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains where the alert object comes from ('the row from lead_alerts or from a push, with its salt') and what passing it returns. It does not name explicit when-not conditions or alternatives, but the usage context is clear enough for selection.

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

All ChainHelix for Machines toolsInspect
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