Skip to main content
Glama

check_password_hygiene

Check password strength locally in memory without logging or sending it anywhere.

Tip: Test a similar pattern rather than pasting your real banking password.

Args:
    password_sample: The password or sample pattern to evaluate.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "password_sample": "<password_sample>"
    },
    "name": "check_password_hygiene"
  }
}

Input Schema

NameRequiredDescriptionDefault
password_sampleYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose important traits: execution is local and in-memory, nothing is logged or sent anywhere. But it never explains how strength is judged, whether any breach/comparison data is consulted, whether results are retained, or how failures are surfaced — a substantial gap for an unannotated tool.

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?

One front-loaded sentence carrying both purpose and the key privacy guarantee, followed by a short actionable tip and a single tight Args line. No redundant or filler content.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and the privacy behavior is well covered. Still, for a security-sensitive tool with zero annotations, the description should say something about how the strength assessment works and what any result means before an agent relays it to a user.

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 0%, and the description names the parameter and clarifies that it may be a real password or a sample pattern to evaluate. That 'pattern sample' framing is genuine meaning beyond the schema, which merely types it as a string. Minor remaining gap: no length or format constraints are mentioned.

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?

States a specific verb and resource: checks password strength. The privacy qualifier (locally in memory, nothing logged or transmitted) further narrows what the tool does. It does not explicitly name a sibling alternative, but the object of the check (a password) is self-evidently distinct from the email/URL/message checking siblings.

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

Usage Guidelines3/5

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

The tip implies how to use it safely (test a similar pattern rather than a real banking password), which is useful implied guidance. However, there is no explicit statement of when to choose this over check_email_breach or analyze_scam_message, and no stated preconditions or exclusions.

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.