TWZRD Agent Intelligence

verify_root_inputs

Read-onlyIdempotent

Independent root verification (see tools/root_verifier.py for the recompute logic).

Input Schema

TableJSON 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	WZRD protocol resource (deposit/claim/settle etc.) for auto-detection and seq hints.
`seller_wallet`	No	Seller wallet for WZRD protocol resource detection.

Output Schema

TableJSON 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.

First observedJul 11, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the read-only nature is clear. The description adds 'via recompute logic' implying computation, but doesn't contradict annotations. Provides minimal extra context.

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?

Extremely concise at two sentences with no waste. Could benefit from slightly more detail, but front-loads the core purpose.

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?

Given 100% schema coverage, output schema present, and annotations, the description is minimally adequate. However, it lacks contextual completeness for a verification tool that might need explanation of what verification entails.

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 has 100% description coverage. The description adds nothing about parameters, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Independent root verification' which identifies the tool's action and resource, but lacks specificity about what 'root' refers to and does not differentiate from sibling tools like verify_receipt.

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?

No guidance on when to use this tool versus alternatives (e.g., verify_receipt). The description provides no context for selection.

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.