Skip to main content
Glama

HIPAA breaches affecting 500+ people from the HHS Office

health_hhs_hipaa_breach_portal
Read-only

HIPAA breaches affecting 500+ people from the HHS Office for Civil Rights portal (last 24 months, under investigation): entity name, state, entity type, individuals affected, submission date, breach type, location of the information and business-associate flag. Newest 100 reports, filterable by state, entity type, breach type, minimum individuals or name; plus total open cases. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "health_hhs_hipaa_breach_portal"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional part of the covered entity name
limitNoRows to return, 1 to 100 (default 50)
stateNoOptional 2-letter state, e.g. CA, TX
breachTypeNoOptional words of the breach type, e.g. hacking, theft, unauthorized
entityTypeNoOptional words of the entity type, e.g. health plan, business associate
minIndividualsNoOptional minimum number of individuals affected

Output Schema

NameRequiredDescriptionDefault
sourceNo
matchesNo
breachesNo
checkedAtNo
openCasesNo
newestShownNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavior beyond that, notably the per-call price ($0.002 via x402/USDC on Base and other networks), the fact that failed calls are not charged, the 24-month/under-investigation data window, and the newest-100 row cap. It also discloses that total open cases are returned alongside the rows, which materially affects how an agent interprets results.

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?

It is a single dense paragraph that front-loads the dataset and scope, then lists fields, then filters and pricing. Nothing is wasted, but the field enumeration overlaps with the existing output schema and makes the sentence long; a tighter structure separating data scope from filters and cost would read better.

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?

For a read-only, paid, filtered list tool with an output schema, the description covers everything an agent needs: data source and time window, row cap and ordering, available filters, extra aggregate output (total open cases), and the cost model including refunds on failure. No significant gap remains.

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 all six parameters are already documented in the schema, including examples for state and breachType. The description adds only light framing — that filters can be combined and that results are the newest 100 reports (relevant to the limit parameter) — without adding syntax or matching semantics beyond the schema, so the baseline 3 applies.

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 names a specific dataset and scope: HIPAA breaches affecting 500+ people from the HHS Office for Civil Rights portal, limited to the last 24 months and cases under investigation. It goes on to enumerate the returned fields (entity name, state, entity type, individuals affected, submission date, breach type, location, business-associate flag), so an agent knows exactly what resource it is retrieving and can distinguish it from unrelated health data siblings.

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?

Usage context is clear: this covers only breaches of 500+ individuals reported in the last 24 months that are under investigation, and results are capped at the newest 100 reports with optional state/entity type/breach type/minimum-individuals/name filters. It does not name an alternative tool or state when not to use it, but given no sibling covers this dataset, the context is sufficient for correct 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.

Resources