AlpineLead OI

Verify Nexus x402 Compact Audit Receipt

verify_nexus_x402_receipt

Read-onlyIdempotent

Public zero-auth MCP verification of a portable Nexus x402 Compact Audit Receipt. Uses 0 credits, 0 AI calls and cannot sign, pay, invoke a buyer, contact a seller or settle a transaction.

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": {
      "compact_receipt": "<compact_receipt>"
    },
    "name": "verify_nexus_x402_receipt"
  }
}

Input Schema

Name	Required	Description	Default
`compact_receipt`	Yes	Complete AlpineLead Nexus Compact Audit Receipt JSON object. Submit the compact receipt only, never Full Evidence JSON. This verification is public, read-only and cannot trigger payment.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 16, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already mark readOnly, idempotent, non-destructive; the description adds concrete behavioral context beyond those annotations: public/zero-auth, 0 credits/AI calls, and the full list of no-op actions. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with no filler; the primary purpose is front-loaded and the second sentence adds only high-value constraints (cost, auth, and excluded side effects).

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

Completeness5/5

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

For a single-parameter read-only verification tool, the annotations, output schema, and parameter schema already carry the return and safety details; the description covers auth, cost, and side-effect exclusions. Nothing an agent needs to invoke it correctly is missing.

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?

The parameter is fully documented in the schema (100% coverage), including the instruction to submit only compact receipt JSON and not Full Evidence JSON. The tool description itself adds only the word 'portable' about the parameter, so baseline 3 applies.

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?

The description states a specific verb and object: 'public zero-auth MCP verification of a portable Nexus x402 Compact Audit Receipt.' It is not a tautology; it adds scope (public, portable, compact) and explicitly lists side-effecting actions it cannot perform, distinguishing it from the many trade/payment sibling tools.

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?

It gives clear context: use as a zero-auth, zero-cost read-only verification, and it enumerates what it cannot be used for (signing, paying, invoking buyers, contacting sellers, settling). It does not name an alternative tool explicitly, so it stops short of a 5.

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

All AlpineLead OI 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.

Resources

Need Help?