Skip to main content
Glama
CyberSafe MCP

CyberSafe MCP

by kshitij9896

check_password_hygiene

Evaluate password strength locally in memory to spot weak patterns and improve password hygiene without sending or logging the password.

Instructions

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 observedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the most consequential trait for a credential tool: evaluation happens locally in memory with no logging and no transmission off-device. It stops short of stating determinism, storage lifetime, or any auth/rate-limit behavior, so it is strong but not exhaustive.

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?

Front-loaded with the core behavior and privacy guarantee in one sentence, followed by a short tip and a one-line arg note. The "Args:" block mildly duplicates the schema, but nothing is padded or buried.

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?

For a one-parameter tool with an output schema already defining return values, the description covers what it does, where it runs, the privacy implications, and how to supply a safe input. Nothing an agent needs in order to invoke it correctly is missing.

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 description coverage is 0%, so the description must compensate for the single parameter, and it does: "The password or sample pattern to evaluate" clarifies that a synthetic pattern is an acceptable value, which the bare schema title "Password Sample" does not convey on its own.

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?

States a specific verb and resource ("Check password strength") plus the execution scope ("locally in memory"), which immediately separates it from siblings like check_email_breach, check_url_safety, and analyze_scam_message that operate on different resources.

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 ("Test a similar pattern rather than pasting your real banking password") gives useful input-handling guidance but is not when-to-use guidance: it never says when this tool should be chosen over the sibling checks or what conditions make it inappropriate.

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