Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_hibp_password_check

Read-onlyIdempotent

Checks whether a password appears in known data breaches via the Have I Been Pwned k-anonymity range API, helping identify compromised credentials without exposing the full password.

Instructions

Check a password against HIBP using its k-anonymity range API.

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": "<password>"
    },
    "name": "oc_hibp_password_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutNo
passwordYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already establish a read-only, idempotent, non-destructive, open-world operation. Naming the k-anonymity range API adds useful implementation and privacy context, but the description does not explain what password-derived data leaves the system or clarify network and timeout behavior.

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?

The single sentence is front-loaded with the action and ends with the distinguishing API mechanism. It contains no filler or redundant restatement of schema fields.

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?

For a simple two-parameter tool with an output schema and clear safety annotations, this is sufficient to infer the basic call using password while optionally omitting timeout. The undocumented parameter, unexplained breach-check purpose, and limited operational detail nevertheless leave noticeable gaps.

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?

With 0% schema description coverage, the description only reinforces that password is the value being checked. It provides no meaning for timeout, such as units, valid range, or the effect of null, and no handling guidance for the sensitive password input.

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 specifies the action ('Check'), resource ('a password'), service ('HIBP'), and method ('k-anonymity range API'). It does not expand HIBP or explicitly state that the purpose is detecting breach-exposed passwords, and it offers no sibling differentiation.

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 wording implies use when an agent wants to test a password against HIBP, but it gives no explicit context such as password breach-exposure screening. There is no when-not guidance, prerequisite information, or named alternative.

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

Deploy Server

Other Tools