Genexxis paid agent tools (x402)

notary_stamp

Timestamp a SHA-256 hash: returns a stored, server-signed receipt (id, hash, label, timestamp, signer, message, signature, verify URL) proving the hash was presented at that time. Price: $0.005 USDC per call, paid with x402 on Base.

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": {
      "hash": "<hash>"
    },
    "name": "notary_stamp"
  }
}

Input Schema

Name	Required	Description	Default
`hash`	Yes	SHA-256 digest of your document, 64 hex chars, optional 0x prefix
`label`	No	Optional label, max 120 chars, no \| character

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 24, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the burden well: it discloses that a receipt is stored and server-signed (a persistent side effect), enumerates the returned fields, and states the cost ($0.005 USDC) and payment rail (x402 on Base). It omits idempotency, whether receipts are permanent/retrievable later, and rate limits.

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 dense sentences: the action and return contract come first, pricing last. No filler, and the most decision-relevant facts (what you get back, what it costs) are front-loaded.

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?

With no output schema, the description compensates by listing the receipt fields, and it covers the payment dimension that the schema cannot. It stops short of explaining how verification works (the verify URL) or whether the receipt is retrievable in later calls.

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%, so both parameters (hash, label) are already fully documented in the schema, including format and the 120-char/| restriction. The description adds nothing beyond that, 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?

States a specific verb and resource ('Timestamp a SHA-256 hash') and spells out the artifact produced (stored, server-signed receipt with named fields). It does not differentiate itself from the sibling notary_time, so an agent must infer which notary tool to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied — you call it when you have a document hash and need proof-of-existence — and the pricing line hints at a paid x402 flow. However, it never says when to use this versus notary_time, nor what prerequisites (wallet, USDC balance on Base) an agent must satisfy first.

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

All Genexxis paid agent tools (x402) 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?