Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

crypto_zk_receipt_verify

[$0.05] Verify verifiable-compute and agent work receipt envelopes using pure Python SHA-256 Merkle commitments, EIP-712/ECDSA checks, and state_attestations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crypto_zk_receipt_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeout_msNoOptional deadline in ms. If the local LLM would exceed it, the response comes back fast with "degraded": true and non-LLM/cached data
proof_envelopeNoJSON proof envelope object (proof_type, leaf, proof[], root, optional signature/signer)
state_commitment_sha256NoExpected 64-hex SHA-256 state commitment to verify against

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden; it does disclose the $0.05 cost and the pure-Python, offline verification approach, which is useful beyond the schema. However, it says nothing about required permissions or keys, whether verification is deterministic/local, or what a failed verification looks like, so the mutation-free safety profile is only implied.

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?

A single front-loaded sentence with the price first and the verification techniques following; no filler. It is dense with cryptographic jargon that could be unpacked, but every clause carries information.

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?

For a three-parameter verifier with a nested envelope object and no output schema, the description does not hint at the result shape (e.g., verified true/false, mismatch reporting) or how the optional state commitment interacts with the envelope. It is enough to recognize the tool's domain but leaves gaps an agent would want filled before calling it blind.

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% and each of the three parameters is documented in-schema, including the proof_envelope structure and the degraded-response behavior of timeout_ms. The description adds no parameter-level meaning (e.g., how state_commitment_sha256 relates to the envelope root), so the baseline 3 applies.

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?

Uses a specific verb ('Verify') with a concrete resource ('verifiable-compute and agent work receipt envelopes') and names the mechanisms (SHA-256 Merkle commitments, EIP-712/ECDSA, state_attestations). An agent can tell this is a cryptographic proof-checking tool, though it does not explicitly contrast itself with the sibling crypto_state_attestation.

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 statement of when to call this versus the closely related crypto_state_attestation or agent_preflight tools, and no prerequisites or exclusions are given. The intended usage must be inferred entirely from the phrase 'verify ... receipt envelopes'.

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.

Resources