Skip to main content
Glama

TWZRD Agent Intelligence

verify_receipt

Read-onlyIdempotent
Free utility: offline-verify a portable v5/v6 trust receipt — the "after you pay"
half of the loop.

Recomputes the Keccak256 leaf from the receipt's preimage (tamper-evidence) AND
verifies the Ed25519 signature against the published TWZRD receipt-signing key
(authenticity). Returns valid/leaf_valid/signature_valid plus the recomputed
leaf and any errors. Pure and offline — no DB, no network, no payment.

Pass the entire PaidReceipt object you were issued. Trust is anchored on the
published key (or expected_pubkey), NOT on whatever pubkey the receipt carries.

max_age_seconds: optional freshness gate (replay protection). Same semantics
as the Python library verify_paid_receipt(..., max_age_seconds=...) and the
standalone CLI --max-age.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
receiptYesThe full v6 PaidReceipt object (leaf + preimage + signature + signing_pubkey) returned by the paid /v1/intel/trust surface.
expected_pubkeyNoOverride the trusted signing pubkey to verify against (default: the published TWZRD receipt key).
max_age_secondsNoIf > 0, reject the receipt if its preimage.timestamp_unix is older than this many seconds (replay/freshness protection, same as CLI --max-age and library).
require_signatureNoRequire and verify the Ed25519 signature (default true). Set false only to inspect an unsigned preview.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
validNoTrue iff the leaf recomputes AND the signature verifies against the trusted key.
domainNoThe V5 domain detected in the preimage.
errorsNoIssues found; empty on success.
leaf_validNoTrue iff the Keccak256 leaf recomputes from the preimage.
provided_leafNoThe normalized leaf supplied in the receipt.
signing_pubkeyNoThe pubkey carried by the receipt.
trusted_pubkeyNoThe published key authenticity was checked against.
recomputed_leafNoThe leaf recomputed from the preimage (0x...).
signature_validNoTrue iff the Ed25519 signature verifies; None if the signature check was skipped.
signature_checkedNoWhether the signature was checked (require_signature).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds behavioral details: offline, no DB/network/payment, returns multiple validity flags and errors, and warns about trust anchoring. Contradictions none.

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?

Well-structured with a bold opening statement. Information is front-loaded and each section adds value. Slightly verbose but not excessive.

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?

Covers inputs, trust model, return values (valid/leaf_valid/signature_valid plus leaf and errors). Output schema exists, so return details are not needed. Complete for a verification tool.

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

Parameters4/5

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

All four parameters have descriptions in the schema (100% coverage). The description adds value by providing source context for receipt, cross-referencing Python library/CLI for max_age_seconds, and usage guidance for require_signature.

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?

Description clearly states the tool's purpose: offline verification of v5/v6 trust receipts. It specifies the actions (recomputes Keccak256 leaf, verifies Ed25519 signature) and distinguishes from sibling tools by focusing on receipt verification.

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?

Provides explicit usage guidance: pass the full PaidReceipt object, trust anchored on published key, and explains optional parameters like max_age_seconds and require_signature. No explicit when-not-to-use, but sufficient for correct invocation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.