Skip to main content
Glama
CyberSafe MCP

CyberSafe MCP

by kshitij9896

check_email_breach

Check whether an email address appears in known public data breaches via XposedOrNot, so users can assess exposure and take protective action; the address is not logged or stored.

Instructions

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

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations at all, the description carries the full disclosure burden. It does add two useful facts: the lookup goes to a third-party service (XposedOrNot) and the address is 'never logged or stored', which matters for privacy-sensitive callers. However it says nothing about authentication requirements, rate limits, error behavior when the service is unavailable, or what a 'breach found' result implies — significant gaps for a tool with zero annotation coverage.

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 purpose sentence is front-loaded and wastes no words; the Args block is somewhat redundant with the schema but earns its place by carrying the 'never logged or stored' note. Overall appropriately sized for a one-parameter tool.

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?

An output schema exists, so return values need not be described. Still, with no annotations and a third-party dependency, the description should note operational constraints (auth, rate limits, failure modes) that an agent needs before invoking it; that omission leaves the definition only marginally sufficient.

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, and it does: the single parameter is explained as the address to check plus a privacy guarantee about non-persistence, which the bare schema does not convey. It stops short of stating accepted formats or validation behavior, keeping it out of the top score.

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 ('check') plus a precisely scoped resource ('email address in known public data breaches') and names the upstream data source (XposedOrNot). This is clearly distinguishable from siblings like check_password_hygiene or check_url_safety, which target different artifacts.

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 use case is implied by the name and first sentence — checking an email against breach data — but there is no explicit when-to-use or when-not-to-use guidance, and no siblings are referenced as alternatives. No prerequisites (API key, rate limits) are mentioned.

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