Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

crypto_blake3

Read-onlyIdempotent

Generate a BLAKE3 hash, keyed-MAC, or key derivation output from text, hex, or base64 input with any output length from 1 to 1024 bytes.

Instructions

BLAKE3 Hash Generator. Compute a BLAKE3 hash of a text string with configurable output length (1-1024 bytes, default 32), in plain-hash, keyed-MAC, or context key-derivation mode. Use crypto_hash instead for MD5/SHA-1/ SHA-256/SHA-512, crypto_sha3 for SHA-3, or crypto_keccak for the pre-standard Keccak used in Ethereum; reach for BLAKE3 when you want the fastest modern hash, an extendable (XOF) digest, a 32-byte keyed MAC, or KDF output from a context string. Runs locally on the input you provide: read-only, non-destructive, deterministic (no random salt), contacts no external service, and is rate-limited (5 requests/min anonymous). Returns the digest as lowercase hex, uppercase hex, and base64, plus the resolved mode, encoding, length, and bit count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesMessage to hash. Interpreted per the encoding field. The empty string is valid (BLAKE3 of empty input is af1349b9f5f9a1a6a0404dea36dcc9499bcb25c9adc112b7cc9a93cae41f3262 at 32 bytes).
encodingNoHow to decode text into bytes before hashing: UTF-8 text, hex, or base64.text
modeNohash = plain BLAKE3 digest; keyed = 32-byte-keyed MAC (requires key); derive-key = KDF from a context string (requires context).hash
lengthNoOutput digest length in bytes (BLAKE3 is an XOF). Defaults to 32 (256-bit).
keyNoKeying material for mode=keyed. After decoding with keyEncoding it must be exactly 32 bytes. Required and used only when mode=keyed; ignored otherwise.
keyEncodingNoHow to decode key into bytes (must yield 32 bytes). Only applies when mode=keyed.text
contextNoApplication-specific context string for mode=derive-key (decoded as UTF-8). Required and used only when mode=derive-key; ignored otherwise.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hashNoDigest as lowercase hex.
hashBase64NoSame digest encoded as standard base64.
uppercaseNoSame digest as uppercase hex.
algorithmNoAlgorithm id, always blake3.
modeNoResolved hashing mode.
encodingNoResolved input encoding applied to text.
keyedNoTrue when mode=keyed (a 32-byte key was applied).
lengthNoOutput length in bytes (1-1024).
bitsNoOutput length in bits (length x 8).
contextNoContext string echoed back; present only when mode=derive-key.
Behavior5/5

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

Beyond annotations (readOnlyHint, etc.), the description adds key behaviors: 'Runs locally on the input you provide: read-only, non-destructive, deterministic (no random salt), contacts no external service, and is rate-limited (5 requests/min anonymous).'

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 well-structured and efficiently conveys purpose, usage guidelines, behavioral traits, and output format without redundancy. Every sentence adds value.

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 (7 parameters, 3 modes), the description covers purpose, usage, behavior, parameters, and output format. Return values are explicitly described as 'digest as lowercase hex, uppercase hex, and base64, plus resolved mode, encoding, length, and bit count.'

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?

Schema coverage is 100%, so the description adds value with context like 'The empty string is valid' and 'BLAKE3 is an XOF' for the length parameter, but most parameter details are already in 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 'BLAKE3 Hash Generator' and explains it computes a hash with configurable modes. It explicitly distinguishes from sibling tools like crypto_hash, crypto_sha3, and crypto_keccak, specifying when to use each.

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 provides explicit alternatives: 'Use crypto_hash for MD5/SHA-1/SHA-256/SHA-512, crypto_sha3 for SHA-3, or crypto_keccak for pre-standard Keccak' and states when to reach for BLAKE3 (fastest modern hash, XOF, keyed MAC, KDF).

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