lazymac-mcp

password_strength

Check password strength by analyzing entropy, crack-time estimates, and common-password patterns using zxcvbn methodology.

Instructions

Entropy, crack-time, common-password check (zxcvbn alt)

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_strength"
  }
}

Input Schema

Name	Required	Description	Default
`params`	No	Free-form params object — passed as query string for GET, JSON body for POST

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 15, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It hints at functionality (entropy, crack-time, common-password check) but lacks details on inputs, outputs, error handling, or performance traits. For a tool with a complex parameter object, this is insufficient to guide the agent effectively.

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?

The description is very concise with a single phrase, which is efficient. However, it's under-specified rather than optimally structured—it could benefit from front-loading the core purpose more clearly, but it avoids unnecessary verbosity.

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?

Given the complexity (1 parameter with nested objects, no output schema, no annotations), the description is incomplete. It doesn't explain what the tool returns, how to interpret results, or provide enough context for the agent to use it correctly, making it inadequate for the tool's likely functionality.

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?

The schema has 100% description coverage, but the description adds no meaningful parameter semantics beyond what the schema provides. The schema describes 'params' as a free-form object, but the description doesn't clarify what specific parameters (e.g., password string) are expected, leaving a gap in understanding despite the high schema coverage.

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

Purpose3/5

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

The description mentions 'Entropy, crack-time, common-password check' which indicates it analyzes password strength, but it's vague about the specific action (e.g., 'calculate' or 'evaluate'). It distinguishes from siblings by noting it's a 'zxcvbn alt', but the purpose isn't clearly stated as a verb+resource combination like 'Evaluate password strength using entropy and crack-time metrics'.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention any context, prerequisites, or exclusions, leaving the agent without direction on appropriate usage scenarios.

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