Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-haveibeenpwned

Haveibeenpwned: Validates an email, computes its SHA1, queries the Pwned Passwords range API and reports a breach boolean 🆓 5 free trial calls per signed wallet

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": "x402-haveibeenpwned"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNo
accountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / account / description
      Removed value: -"Account to process"
    • removedInput schema / properties / email / description
      Removed value: -"Email to process"
  2. First observed

TDQS

B3.1/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 real behavior: the SHA1 hashing implies the email itself is not sent in the clear (a privacy property), the response is a breach boolean, and there is a hard rate/cost limit tied to a signed wallet. It omits auth details beyond 'signed wallet' and says nothing about failure modes or what happens when the free calls are exhausted.

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?

A single front-loaded sentence that puts the resource and the outcome first, with the pricing note appended. The SHA1/range-API detail is arguably more mechanism than an agent needs, but it is compact and defensible.

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?

For a tool with no annotations, no output schema, and 0% schema coverage, the description should disambiguate its two parameters and the email-vs-password semantics. It leaves 'account' entirely unexplained and never clarifies whether the breach check is on an email address or a password, which is the single most important thing to know before calling it.

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?

Schema description coverage is 0% for both parameters. The description explains 'email' loosely but says nothing about 'account' (alias? alternative identifier? required together?), even though the schema marks neither parameter as required, which is itself ambiguous. With two undocumented params and no compensating explanation, this is a significant gap.

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 concrete pipeline: validate an email, hash it, query the Pwned Passwords range API, return a breach boolean. That is far more specific than a tautology, but it never distinguishes itself from siblings like x402-password-leak, x402-validate-email, or x402-email-verify, and the mechanism is muddled (Pwned Passwords is a password-hash API, while the input described is an email).

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?

There is no when-to-use or when-not-to-use guidance and no named alternative among the many email/password/security siblings. The only usage-shaped information is a pricing constraint ('5 free trial calls per signed wallet'), which tells the agent about cost, not about tool selection.

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.