Skip to main content
Glama

x420_evidence_timestamp

Creates SHA-256, SHA-512, and Keccak-256 fingerprints of text or base64 bytes with an ISO observation time and signed receipt, giving verifiable proof that data existed at a moment.

Instructions

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. PAID: $0.01 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: sha256, sha512, keccak256, bytes, observed_at, statement, note - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"text":"Roof inspection photo set 2026-11-07, 14 files","label":"claim 4471 photos"}.

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 observedv1.0.2

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false; the description goes well beyond that by disclosing real-money cost ($0.01 USDC on Base via x402), the wallet env var required, the settlement transaction returned, the ed25519 receipt, and the scope limits of what the timestamp legally means. The non-idempotent and non-read-only hints are consistent with a per-call paid settlement, so nothing is contradicted.

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?

The deliverable, the paid step, the scope disclaimers and the return shape are front-loaded, and most sentences carry distinct information. The run of 'not professional, legal, insurance, engineering, medical, financial or tax advice' is boilerplate that could be compressed, but it is short and relevant to an evidence-framing 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?

There is no output schema, but the description enumerates the returned fields (sha256, sha512, keccak256, bytes, observed_at, statement, note) plus the signed receipt and settlement transaction. With payment, prerequisites, scope limits and example input all present, an agent has everything needed to call this correctly.

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 text, base64 and label are already documented by the schema, including the 'supply base64 instead' exclusivity note. The description reinforces the text-or-base64 choice and supplies a concrete example input, but adds no encoding or format detail (e.g. standard vs URL-safe base64) beyond structured data, so the baseline of 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 first sentence names a specific verb and resource — sha256/sha512/keccak256 fingerprinting of supplied text or base64 bytes, combined with the provider's ISO time and an observation statement under an ed25519-signed receipt. It also distinguishes itself from adjacent capabilities by noting that on-chain anchoring is a separate paid step, so an agent can tell it apart from hash-only or chain-proof siblings without opening another schema.

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 explicit bounds: on-chain anchoring is a separate step, and the tool is 'not a notarisation or legal timestamp,' which tells the agent when the output is insufficient for a legal purpose. What it lacks is a named routing alternative (e.g. pointing to the plain hash digest or the proof-of-payment tool for the anchoring step), so the when-to-use guidance is clear but not fully comparative.

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