Skip to main content
Glama

check_email_breach

Check if an email address appeared in known public data breaches via XposedOrNot.

Args:
    email: The email address to check (never logged or stored).

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": {
      "email": "<email>"
    },
    "name": "check_email_breach"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It adds two useful behavioral facts: the query is delegated to a third-party service (XposedOrNot) and the email is 'never logged or stored'. It does not mention rate limits, failure modes for malformed addresses, or whether results are cached, and the return shape is covered by the output schema.

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?

The core purpose is front-loaded in one sentence with no preamble. The 'Args:' block partially restates the schema, but the privacy note inside it earns its place.

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

Completeness4/5

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

For a one-parameter read tool with an output schema, the description covers what it does, the data source, and the privacy handling. Remaining gaps (error behavior, rate limits, freshness of breach data) are minor rather than blocking.

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% — the single property is just a string titled 'Email' with no description — so the description must compensate. It does, clarifying that the parameter is the address to check and adding a privacy guarantee ('never logged or stored') that the schema does not convey.

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 states a specific verb ('Check') and a precise resource ('an email address appeared in known public data breaches'), and names the upstream data source (XposedOrNot). The resource differs plainly from siblings like check_password_hygiene and check_url_safety, though no sibling is named explicitly.

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?

Usage is only implied by the purpose statement — an agent can infer it should call this when it has an email address and wants breach exposure. There is no explicit when-to-use, when-not-to-use, or routing guidance toward the sibling checks.

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.