Skip to main content
Glama

Hibp

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Check Password Prefix

check_password_prefix
Read-onlyIdempotent

Direct k-anonymity lookup: pass the first 5 hex chars of a SHA-1 password hash, get back all SHA-1 suffixes with their pwned counts. Use this if you're hashing client-side and only want to send the prefix.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sha1_prefixYes5 hexadecimal characters

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
suffixesYesArray of suffix/count pairs matching this prefix
sha1_prefixYesThe 5-character SHA-1 prefix provided
suffix_countYesNumber of matching SHA-1 suffixes found

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "sha1_prefix": "21BD1"
+  },
+  {
+    "sha1_prefix": "CBFDA"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "sha1_prefix": {
+      "description": "The 5-character SHA-1 prefix provided",
+      "type": "string"
+    },
+    "suffix_count": {
+      "description": "Number of matching SHA-1 suffixes found",
+      "type": "number"
+    },
+    "suffixes": {
+      "description": "Array of suffix/count pairs matching this prefix",
+      "items": {
+        "properties": {
+          "count": {
+            "description": "Number of times this hash seen in breaches",
+            "type": "number"
+          },
+          "suffix": {
+            "description": "SHA-1 suffix (35 hex chars after prefix)",
+            "type": "string"
+          }
+        },
+        "required": [
+          "suffix",
+          "count"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "sha1_prefix",
+    "suffix_count",
+    "suffixes"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds value by explaining the k-anonymity mechanism and that the tool returns multiple suffixes and counts, which is beyond what annotations provide. No contradiction.

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?

Two sentences with no wasted words. All information is front-loaded. Every sentence adds value.

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 simple tool with one parameter, a clear description, and an output schema, the description fully covers the tool's behavior and use case. No gaps.

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 100%, so baseline is 3. The description adds meaning by stating the parameter is a 'prefix of a SHA-1 password hash', which is richer than the schema's '5 hexadecimal characters'. This helps the agent understand the context.

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?

The description clearly states the tool performs a k-anonymity lookup using the first 5 hex chars of a SHA-1 password hash and returns SHA-1 suffixes with pwned counts. It uses specific verbs and resources, and the purpose is unambiguous.

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

Usage Guidelines4/5

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

The description explicitly advises using this tool 'if you're hashing client-side and only want to send the prefix', providing clear context for when to use it. However, it does not explicitly mention when not to use it or name alternative tools.

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

All Hibp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources