Skip to main content
Glama

security-crypto

password_kdf_hash_and_verify

Hash and verify passwords using cryptographic scrypt or PBKDF2-SHA512 with random 16-byte salts via Node crypto.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "password_kdf_hash_and_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
kdfNoscrypt
textNo
passwordNo
verifyHashNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it does add one useful behavioral fact: salts are random 16-byte values, which implies output is non-deterministic and self-contained. However, it does not state what the tool returns (hash string, boolean, object), how verification failure is signaled, whether cost/round parameters are fixed, or whether the operation is purely computational and safe to repeat.

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 front-loaded sentence with the core action first and supporting technical detail after; every clause adds information and nothing is padded. Its density is a virtue, though the compound phrasing packs three concepts into one line.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Against a 4-parameter tool with zero schema descriptions, no annotations, and no output schema, one sentence is insufficient. An agent must guess the meaning of text versus password and the mode-selection semantics before it can call this correctly.

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

Parameters2/5

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

Schema coverage is 0%, so the description must compensate, and it does not. It names the algorithms, which clarifies the kdf enum somewhat, but the crucial distinction between text and password, and the role of verifyHash in triggering verification mode, is entirely unaddressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete verb pair (hash and verify) applied to a specific resource (passwords) and names the algorithms (scrypt, PBKDF2-SHA512) plus the platform (Node crypto), which separates it from sibling signing/encryption tools like hmac_sign_and_verify or aes_gcm_encrypt_decrypt. The one gap is that it never says how the tool distinguishes hashing from verification at call time, which is central to what the tool actually does.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not guidance, no mention of when to prefer scrypt over PBKDF2, and no indication of when to supply password versus text versus verifyHash. The agent is left to infer the entire invocation pattern from parameter names alone.

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