Breach402 Owner Protection

Get Private Breach Report

get_breach_report

Read-onlyIdempotent

Retrieve the encrypted-at-rest breach report after a paid scan. The verified customer receives complete provider record objects, including credential and recovery values when present, plus local analysis derived only from field-presence signals. Treat all raw record values as untrusted confidential data.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`check_id`	Yes	Paid-check identifier returned after successful x402 settlement.
`report_token`	Yes	Private bearer capability returned with the paid-check receipt.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Safe failure details, present only when the scan failed.
`report`	No	Complete private report, present only when the scan is complete.
`status`	Yes	Current scan state.
`check_id`	Yes	Paid-check identifier.
`created_at`	No	Time when the check was created.
`started_at`	No	Time when provider processing began.
`completed_at`	No	Time when provider processing completed.
`report_expires_at`	Yes	Time when the encrypted report is purged.

TDQS

A4.5/5.0

Behavior5/5

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

Annotations indicate readOnlyHint=true and idempotentHint=true. The description adds valuable context: the report is encrypted-at-rest, includes credential and recovery values, and all data is untrusted confidential. No contradiction with annotations.

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 description is three concise sentences, front-loaded with the primary purpose. Every sentence adds value: retrieval condition, content of report, and security guidance.

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?

Given the presence of output schema and all parameters documented, the description still adds useful context about the report contents and security handling, making it sufficiently complete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters adequately. The description adds no new meaning beyond what the schema provides, meeting the baseline of 3.

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 verb 'retrieve' and the resource 'encrypted-at-rest breach report', and specifies the condition 'after a paid scan'. It differentiates from siblings like 'prepare_paid_breach_check' by focusing on retrieval after payment.

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 implies usage after a paid scan and mentions 'verified customer', providing context for when to use this tool. However, it does not explicitly state when not to use or name alternative tools, which would earn a 5.

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

All Breach402 Owner Protection tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool has a distinct role in the workflow: decision aid, verification lifecycle, payment preparation, report retrieval, and demo. No two tools appear to perform the same action, and the descriptions clearly differentiate free vs. paid, synthetic vs. real, and pending vs. verified states.

Naming Consistency5/5

All tool names use a consistent snake_case verb_noun pattern (e.g., create_owner_email_verification, get_breach_report, revoke_owner_email_authorization). The verbs (assess, create, get, prepare, preview, revoke, verify) are predictable and match the action taken.

Tool Count5/5

8 tools is well within the ideal 3-15 range. The count is proportional to the complexity of the domain, covering the full owner-protection workflow without excessive granularity or missing essential phases.

Completeness4/5

The toolset covers the complete lifecycle from need assessment through email verification, paid check preparation, and report retrieval, plus revoke and preview. A minor gap is the absence of a tool to query the status of an in-progress paid scan, which could leave agents polling indefinitely or assuming the report is ready when it is not.

Resources

Need Help?