Skip to main content
Glama

X420 agent services

x420_evidence_timestamp

Read-onlyIdempotent

Evidence fingerprint and timestamp: sha256 / sha512 / keccak256 of supplied text or base64 bytes with the provider's ISO time and a statement of observation, delivered under the agent's ed25519-signed receipt. On-chain anchoring is a separate paid step. Not a notarisation or legal timestamp. Not professional, legal, insurance, engineering, medical, financial or tax advice. Price: $0.01 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: sha256, sha512, keccak256, bytes, observed_at, statement, note.

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": "x420_evidence_timestamp"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoUTF-8 text to fingerprint (default: none; supply base64 instead)
labelNofree-text label echoed back (default: none)
base64Nobase64 bytes to fingerprint (default: none; supply text instead)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it discloses the $0.01 USDC price on Base, that the hosted tool does NOT pay and does NOT return the deliverable, and the exact x402 exchange (GET the url, read PAYMENT-REQUIRED from the 402, retry with PAYMENT-SIGNATURE, x402 v2). It also enumerates the deliverable fields once paid (sha256, sha512, keccak256, bytes, observed_at, statement, note) and lists explicit non-claims.

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

Conciseness3/5

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

Purpose and payment status come first, then the x402 mechanics, which is the right order. But the text is dense and multi-clause, and the blanket 'not professional, legal, insurance, engineering, medical, financial or tax advice' sentence burns a full line on boilerplate that does little to help an agent invoke the tool.

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?

With no output schema, the description compensates by listing the exact deliverable keys. It covers pricing, the two execution paths, the 402 handshake, and what the tool is not, so an agent has everything needed to call it and interpret the response after payment.

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%, so the three parameters are already documented and the baseline is 3. The description only echoes the text/base64 input choice and adds nothing about the 'label' echo, mutual exclusivity handling, or empty-input behavior beyond what the schema states.

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?

The description uses a specific verb and resource: hash a text or base64 payload with sha256/sha512/keccak256 and attach the provider's ISO time plus an observation statement under an ed25519-signed receipt. That composite output distinguishes it in substance from a plain hashing tool, and it states its scope limits ('On-chain anchoring is a separate paid step. Not a notarisation or legal timestamp'). It never names the sibling hash/digest-style tool it most overlaps with, so differentiation is inferred rather than explicit.

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 by the purpose plus the exclusions (not notarisation, not legal timestamp, not advice), and the payment fork is clear: the hosted tool only validates and returns payment instructions, while the local x420-mcp server pays automatically. It gives no explicit routing rule for when an agent should pick this over a sibling digest or other x420 tool, so selection guidance stays implicit.

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