Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

crypto_sha3_generator

Read-onlyIdempotent

Compute SHA3 cryptographic digests (224/256/384/512) from text, hex, or Base64 input. Returns hex hash with length and security level.

Instructions

SHA3 Hash Generator (SHA3-224/256/384/512). Compute a SHA3 (Keccak, NIST FIPS 202) cryptographic digest of text, hex, or Base64 input. Choose algorithm to pick the variant (SHA3-256 default); set inputFormat to decode the input before hashing. Use this for the standardized SHA3 sponge family; use crypto_keccak_generator for the pre-standard Ethereum Keccak-256 variant, or crypto_hash for MD5, SHA-1, and SHA-2 legacy digests. Runs locally on the input you provide: read-only, non-destructive, contacts no external service, and is rate-limited (30 requests/minute for anonymous callers). Returns the lowercase hex digest plus its length, output size, security level, and typical use cases.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesData to hash, interpreted per inputFormat (plaintext, hex, or Base64). Empty string hashes to the variant fixed-empty digest.
algorithmNoSHA3 variant determining digest width (224, 256, 384, or 512 bits). Case-insensitive.sha3-256
inputFormatNoHow to decode input before hashing. hex requires even-length valid hex; base64 requires a valid Base64 string.text

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputNoThe submitted input, echoed back.
inputFormatNoThe decoding applied (text, hex, or base64).
algorithmNoThe variant used, uppercased (such as SHA3-256).
hashNoLowercase hexadecimal digest.
hashLengthNoNumber of hex characters in hash (twice the byte length).
outputSizeNoDigest size in bits and bytes (such as 256 bits / 32 bytes).
descriptionNoHuman-readable summary of the variant.
securityLevelNoCollision-resistance level (such as 128-bit security).
useCasesNoTypical applications for the variant.
Behavior5/5

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

Annotations already declare read-only, non-destructive, idempotent. The description adds important behavioral context: runs locally, contacts no external service, rate-limited (30 req/min for anonymous). No contradiction with annotations.

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?

The description is two sentences plus a usage clause, all front-loaded. Every sentence adds value without redundancy. It efficiently conveys purpose, usage, and behavioral details.

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 tool's complexity (3 params, enums, output schema present), the description covers all essential aspects: purpose, supported algorithms, input formats, usage guidance, safety, rate limits, and return information (hex digest, length, security level, use cases). It is complete for effective decision-making.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage. The description adds value by explaining the algorithm parameter (choose variant, SHA3-256 default) and inputFormat (decode before hashing). It also notes empty string hashes to the fixed empty digest, which is beyond the schema.

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 SHA3 hashes (SHA3-224/256/384/512) from text, hex, or Base64 input. It distinguishes itself from crypto_keccak_generator and crypto_hash, making its purpose unambiguous.

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?

The description explicitly tells when to use this tool (standardized SHA3) and when to use alternatives (crypto_keccak_generator for Ethereum Keccak-256, crypto_hash for legacy hashes). This provides excellent guidance for correct tool selection.

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