TWZRD Agent Intelligence

verify_root_inputs

Read-onlyIdempotent

Independent root verification: recomputes the leaves, dataset hash and root from the public root data.

Input Schema

Name	Required	Description
`root_seq`	No	Specific root sequence to verify. If omitted, best-effort resolution via resource metadata or latest.
`resource_name`	No	Legacy on-chain protocol resource (deposit/claim/settle) for auto-detection and seq hints.
`seller_wallet`	No	Seller wallet for legacy on-chain protocol resource detection.

Output Schema

Name	Required	Description
`error`	No	Error message on the ERROR path; null on PASS/FAIL.
`status`	No	"PASS" = recomputed GLOBAL_V5 leaves + dataset_hash + sorted-pair root match the published values. "FAIL" = mismatch (do not trust the root). "ERROR" = could not run (fetch failure / missing data).
`root_seq`	No	Root sequence number that was verified.
`leaf_count`	No	Number of leaves (users) in the verified root.
`onchain_match`	No	Always null: this tool does NOT read Solana/the AO program. Use server_consistent for the recompute result; do not gate on-chain actions on this field expecting a chain anchor.
`leaf_hash_match`	No	True iff every server-provided leaf_hash matches the locally recomputed value.
`recomputed_root`	No	Independently recomputed sorted-pair keccak256 merkle root (hex).
`server_consistent`	No	True iff the recomputed root/dataset_hash matches the value the SERVER published alongside its own leaves (self-consistency). NOT an on-chain check. Null when not comparable.
`recomputed_dataset_hash`	No	Independently recomputed keccak-concat dataset_hash (hex).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 20, 2026

changedInput schema / properties / resource_name / description

Previous value: -"WZRD protocol resource (deposit/claim/settle etc.) for auto-detection and seq hints."New value: +"Legacy on-chain protocol resource (deposit/claim/settle) for auto-detection and seq hints."

changedInput schema / properties / seller_wallet / description

Previous value: -"Seller wallet for WZRD protocol resource detection."New value: +"Seller wallet for legacy on-chain protocol resource detection."

First observedJul 11, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds that the verification is independent and recomputes values from public data, which clarifies the trust model, but it does not cover permissions, rate limits, or return behavior beyond what the output schema provides.

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 description is a single front-loaded sentence with no wasted words. It is appropriately concise, though its brevity leaves little room for structural aids such as usage context.

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

Completeness3/5

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

The tool has an output schema and annotations covering safety and idempotence, so return-value and safety details need not be repeated. However, the description omits any usage guidance or prerequisites, which would be valuable for an agent choosing among several verification tools.

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%, so the input schema already fully documents all three optional parameters. The description adds no parameter-level meaning, which is acceptable given the schema's completeness, but it does not enhance semantics.

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 gives a clear verb ('verification') and specific method ('recomputes the leaves, dataset hash and root from the public root data'). It distinguishes the operation as root verification, but does not explicitly differentiate itself from sibling verification tools like verify_receipt or verify_x402_settled_claim.

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?

There is no explicit guidance on when to use this tool versus alternatives. It implies verification is needed, but does not state prerequisites, exclusions, or when a different verify tool is more appropriate.

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

All TWZRD Agent Intelligence tools Inspect

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.