Skip to main content
Glama

Nalvorn Checks

receipt_verify

Read-only

Verify a receipt: canonical JSON digest and declared sha256 Costs 0.01 USDC per call on Base (x402). Call it over HTTP with a PAYMENT-SIGNATURE header to actually run it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "payload": "<payload>",
      "sha256": "<sha256>"
    },
    "name": "receipt_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
sha256YesExpected sha256 digest, hex, 64 characters
payloadYesObject whose canonical JSON is the signed receipt payload

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds critical behavior the annotations cannot convey: a 0.01 USDC charge per call on Base via x402 and a mandatory PAYMENT-SIGNATURE header over HTTP. It does not state what happens on payment failure or on digest mismatch, which keeps it below a 5.

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?

Three short clauses with the core purpose front-loaded and no padding. Minor punctuation issues ('declared sha256 Costs 0.01...') slightly hurt readability but not comprehension.

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?

Payment and transport requirements are well covered, but with no output schema the description never says what verification returns (boolean, verdict object, error shape), which is the main thing an agent needs after calling. Adequate for a 2-parameter tool, but with a clear gap.

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 coverage is 100% and both parameters are fully described in the schema, so the baseline is 3. The phrase 'canonical JSON' hints that payload is canonicalized before hashing, which adds a little meaning, but the sha256 parameter is only restated, not elaborated.

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?

States a specific verb and resource ('Verify a receipt') plus the mechanism ('canonical JSON digest and declared sha256'), so an agent knows exactly what operation is performed. It does not explicitly differentiate itself from siblings like verify_manifest or payment_verdict, so it stops short of a 5.

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?

The description explains how to invoke the tool (HTTP + PAYMENT-SIGNATURE header, x402 cost) but gives no guidance on when to choose this over verify_manifest, payment_verdict, or other verification siblings. An agent must infer the selecting condition entirely from the tool name.

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