Skip to main content
Glama

X420 agent services

x420_hash_digest

Read-onlyIdempotent

Hash digest: sha256 / sha512 / sha1 / md5 / keccak256 of supplied text or base64 bytes. Pure computation, nothing stored. 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: algorithm, bytes, digests{alg: hex}.

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_hash_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoUTF-8 text to hash (default: none; supply base64 instead)
base64Nobase64-encoded bytes to hash (default: none; supply text instead)
algorithmNosha256 (default), sha512, sha1, md5, keccak256 or all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag readOnly/idempotent/non-destructive, but the description adds the decisive behavior the annotations cannot convey: it costs $0.01 USDC per call via x402 on Base, it does not itself pay, and it returns payment instructions rather than the digest. The post-payment return shape (algorithm, bytes, digests map) is also disclosed. All of this is consistent with readOnlyHint=true and openWorldHint=true.

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?

Purpose and cost model are front-loaded in a tight opening, and the payment mechanics are dense but necessary. The one stretch of dead weight is the 'not professional, legal, insurance, engineering, medical, financial or tax advice' disclaimer, which consumes space without helping an agent decide or call.

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 steps in to describe the paid deliverable's JSON shape and the unpaid response (pay_to, network, price, x402 URL). For a stateless hashing tool with a metered payment path, nothing an agent needs to call 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?

Schema description coverage is 100%, with each property already documenting itself, including the text/base64 mutual exclusivity and the sha256 default. The description repeats the algorithm list and input forms but adds no syntax, encoding, or edge-case detail beyond the schema, so the 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 first sentence names the concrete resource (hash digest) and enumerates the exact algorithms and input forms (text or base64 bytes). It is unmistakable against every sibling, which serve entirely different domains such as geocoding, DNS, or currency conversion.

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?

The definition clearly frames the two operating modes: the hosted tool only validates input and returns payment instructions, while the local x420-mcp server with a wallet key pays automatically. It even sketches the x402 retry sequence. What it lacks is any explicit exclusion or comparison against neighboring utilities (e.g. when a plain checksum is preferable to x420_evidence_timestamp).

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