Skip to main content
Glama

x420_hash_digest

Computes SHA-256, SHA-512, SHA-1, MD5, or Keccak-256 digests from supplied text or base64 bytes for integrity checks; returns hex digests and a signed receipt as JSON.

Instructions

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. PAID: $0.01 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: algorithm, bytes, digests{alg: hex} - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"text":"hello","algorithm":"all"}.

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

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the commercial model ($0.01 USDC per call on Base, real money), the required credential (X420_MCP_WALLET_PRIVATE_KEY), and that the response includes a signed receipt and settlement transaction. This is important context: the annotations mark readOnlyHint=false and openWorldHint=true, and the description explains why (on-chain payment settlement) rather than leaving the agent to guess at a write side effect. The 'nothing stored' claim is scoped to the digest computation, not to the disclosed settlement.

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?

The operational content is front-loaded and efficient: algorithm list, purity, price, credential, return shape, example. The long 'Not professional, legal, insurance, engineering, medical, financial or tax advice' disclaimer is boilerplate that does not help an agent select or invoke the tool and consumes a full sentence of a short description.

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?

For a stateless hashing utility with full schema coverage and no output schema, the description covers price, credential, and return payload (algorithm, bytes, digests, receipt, tx), which is more than most. One gap remains: all three parameters are optional, yet the description never says what happens if neither text nor base64 is supplied, leaving an edge case undefined.

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 all three parameters are already self-documenting; the description only reinforces this with an example input using {"text":"hello","algorithm":"all"}. The valuable detail — that 'all' is a valid algorithm selector and that text and base64 are substitutes — is already in the schema, so the description adds little beyond a usage sample.

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?

States a specific operation and resource — 'Hash digest: sha256 / sha512 / sha1 / md5 / keccak256 of supplied text or base64 bytes' — including the supported algorithm set and accepted input forms. An agent can immediately tell this is the hashing tool and not confuse it with siblings like x420_id_generate or x420_units_convert.

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 description ('Pure computation, nothing stored' and the example input), which tells the agent this is a stateless one-shot computation rather than something to sequence. However, there is no explicit when-to-use/when-not guidance, no statement about choosing between text and base64 inputs, and no named alternative for any overlapping need.

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