Skip to main content
Glama

Generate MD5, SHA and CRC-32 hashes of text

hash
Read-only

Hashes of a text or base64 input (up to 1 MB): MD5, SHA-1, SHA-256, SHA-384, SHA-512 and CRC-32, and HMAC-SHA-256 or HMAC-SHA-512 when a key is given. Hex and base64 output. MD5 and CRC-32 are implemented here and checked against RFC 1321 and the standard CRC test vector. Body { input, encoding, algorithms, key }. Pure code and WebCrypto, no outside request. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
keyNoKey for the HMAC algorithms, up to 1024 characters (JSON body field)
inputYesThe text, or base64 when encoding is base64 (JSON body field)
encodingNotext (default) or base64
algorithmsNoComma-separated: md5, sha1, sha256, sha384, sha512, crc32, hmac-sha256, hmac-sha512 (default: all but the HMACs)

Output Schema

NameRequiredDescriptionDefault
bytesNo
sourceNo
resultsNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description adds substantial context: cost of $0.002 per successful call, failed calls not charged, payment via x402, no outside requests, and the implementation trust note about RFC 1321 and CRC test vectors. It stops short of describing error behavior for oversized input or invalid algorithm names, which keeps it from a 5. Note a mild tension with openWorldHint=true, but the 'no outside request' claim concerns data fetching rather than the payment path, so it is not a contradiction.

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?

A single dense paragraph that front-loads capability, algorithms, and limits before the implementation and pricing details. Some algorithm enumeration duplicates the schema, and the pricing/network list at the tail is verbose, but every clause carries usable information.

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?

An output schema exists, so return formats need not be explained, and the description covers everything else an agent needs: size ceiling, input encoding, algorithm selection and defaults, HMAC keying, cost model, and isolation from external calls. Nothing required for a correct invocation 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%, so all four fields (input, encoding, algorithms, key) are already documented in the schema, including defaults and the 1024-character key limit. The description largely restates the algorithm list and the key-triggers-HMAC rule rather than adding new syntax or format detail, 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?

Opens with a specific verb and resource ("Hashes of a text or base64 input") and enumerates exactly which algorithms are produced (MD5, SHA-1/256/384/512, CRC-32, HMAC variants). It also states the 1 MB input ceiling, so an agent knows the scope and limits without opening the 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?

The description gives clear conditional guidance: HMAC algorithms are produced "when a key is given," base64 input applies "when encoding is base64," and the default algorithm set excludes HMACs. It does not name when to avoid this tool or point to a sibling alternative, but no plausible hashing alternative exists in the sibling list, so the gap is minor.

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