Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

crypto_hash

Read-onlyIdempotent

Compute one or more hash digests (MD5, SHA, CRC32, Adler32) from UTF-8 text. Returns hex strings for each algorithm in a single call.

Instructions

Cryptographic Hash Generator (MD5, SHA, CRC32, Adler32). Compute one or more hash digests of a UTF-8 text string in a single call. Supports MD5, SHA-1, SHA-256, SHA-512 cryptographic hashes plus CRC32 and Adler32 checksums, returned as a lowercase or uppercase hex string per algorithm. Use crypto_hash for general text digests; use crypto_checksum for the wider non-cryptographic checksum set (Fletcher, FNV, CRC variants), crypto_hmac for keyed message authentication, or crypto_hash_identifier to detect an unknown hash's algorithm. Runs locally on the input you provide: deterministic, read-only, non-destructive, contacts no external service, and is rate-limited. Returns a map of algorithm id to hex digest, the algorithms that produced output, the output format, and the input byte length.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe UTF-8 text to hash. Hashed as raw bytes; an empty string is permitted and yields each algorithm's empty-input digest.
algorithmsYesOne or more algorithm ids to compute. Also accepts an object map of id to boolean. Unknown ids are silently skipped; if none are valid it falls back to md5 and sha256.
outputFormatNoHex digit case for every digest: "hex" for lowercase, "HEX" for uppercase. Any other value is treated as "hex".hex

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hashesNoMap of algorithm id (md5, sha1, sha256, sha512, crc32, adler32) to its hex digest; algorithms not requested have an empty-string value.
algorithmsNoAlgorithm ids that produced a digest (unknown ids dropped).
outputFormatNoThe normalized hex case applied (hex or HEX).
inputLengthNoByte length of the input text.
Behavior5/5

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

Beyond annotations (readOnlyHint, destructiveHint, idempotentHint), the description adds local execution, determinism, no external service contact, rate-limiting, and return structure, fully disclosing behavior.

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

Conciseness5/5

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

Three sentences covering purpose, usage, behavior, and return value with no unnecessary words, well structured and front-loaded.

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?

Given the presence of an output schema, the description adequately explains inputs, outputs, and behavioral context, leaving no gaps for selection and invocation.

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 covers all parameters with descriptions, defaults, and enums. The description adds minimal meaning beyond the schema, e.g., noting hex case, but this is already in the outputFormat parameter description.

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 description clearly states the tool computes hash digests of a UTF-8 string, lists supported algorithms, and distinguishes from siblings like crypto_checksum, crypto_hmac, and crypto_hash_identifier.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells when to use this tool vs alternatives: 'Use crypto_hash for general text digests; use crypto_checksum for...', providing clear decision guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server