Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

crypto_argon2

Read-only

Hash plaintext passwords using Argon2 KDF. Returns a PHC-encoded hash with parsed parameters and a fresh salt per call.

Instructions

Generate Argon2 Password Hash. Hash a plaintext password with the Argon2 memory-hard KDF, returning a self-describing PHC-encoded hash plus the parsed parameters and salt. A fresh random salt is generated on every call, so the same input yields a different hash each time (non-idempotent). Use this to create a new hash; use crypto_argon2_verify to check a password against an existing one. Argon2 is the recommended modern KDF — prefer it over crypto_bcrypt (no memory hardness), crypto_scrypt, and the legacy crypto_pbkdf2. Runs server-side on the input you provide: read-only, non-destructive, contacts no external service, and is rate-limited (5 requests/min, 30/hour, 100/day for anonymous callers; CAPTCHA may trigger above 20/hour). Returns the encoded hash, the variant, the m/t/p cost options, and the salt/length parsed back out.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passwordYesThe plaintext password to hash. Required and must be non-empty.
variantNoArgon2 variant. argon2id (hybrid, recommended) resists both side-channel and GPU attacks; argon2i is data-independent only.argon2id
memoryNoMemory cost in KiB (the m parameter). Higher is stronger but slower.
timeNoTime cost / number of iterations (the t parameter).
threadsNoDegree of parallelism / threads (the p parameter).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
passwordNoThe plaintext password that was hashed (echoed from the request).
hashNoThe encoded Argon2 hash in PHC format: $argon2id$v=19$m=65536,t=4,p=3$<saltBase64>$<hashBase64>.
variantNoThe variant used to hash, argon2id or argon2i.
variantNameNoHuman-readable variant label, e.g. Argon2id.
optionsNoThe cost parameters applied to the hash.
infoNoComponents parsed back out of the encoded hash.
lengthNoCharacter length of the encoded hash string.
generatedAtNoISO 8601 timestamp of when the hash was generated.
verifiedNoAlways true — a self-check that the generated hash verifies against the input password.
Behavior5/5

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

Adds important behavioral context beyond annotations: fresh random salt per call (non-idempotent), server-side execution, read-only nature, no external service contact, rate limits (5/min, 30/hr, 100/day). Annotations already declare readOnlyHint=true and idempotentHint=false, but description enriches with specifics.

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?

Description is well-structured with title, purpose, usage guidance, comparisons, and behavioral notes. It packs substantial information but remains readable; minor trimming could improve conciseness.

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 (5 params, output schema, annotations), the description fully covers purpose, usage, behavior, rate limits, and alternatives. No significant gaps.

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 coverage is 100% with detailed descriptions, examples, enums, and defaults for all 5 parameters. Description adds minimal extra meaning beyond schema (e.g., 'required and non-empty' for password). Baseline 3 is appropriate.

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?

Description clearly states 'Generate Argon2 Password Hash' and explains the exact function: hash a plaintext password with Argon2 KDF, returning PHC-encoded hash plus parsed parameters. It distinguishes from sibling crypto_argon2_verify and other crypto tools like crypto_bcrypt.

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 (create new hash) vs. crypto_argon2_verify (check password). Recommends Argon2 over bcrypt, scrypt, pbkdf2, providing clear alternative 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