Skip to main content
Glama

Breach to Claim: data breach settlements

Am I owed money from a data breach? Find the open settlement, deadline and payout

find_breach_settlement
Read-onlyIdempotent

For 'I got a data breach notice from X', 'am I owed money from the X data breach', 'is there a settlement for X', 'how do I claim the X settlement', 'is this settlement letter real'. Matches the company against open class-action data-breach and privacy settlements, each read off its official court-authorized website: the claim deadline and days left, what it pays (documented losses up to $X, cash payment, credit monitoring), the class definition verbatim so the person can see if they are in it, whether the code printed on the notice letter is needed, the case and court, the official claim site, and a link to a page with their claim checklist filled in. If no settlement is open it says so, and lists the breach notices on public record (California and Washington AG) so the person knows the breach is real and to keep the letter. It takes the company name only: no Social Security number, notice ID, claim ID or name is needed or taken. This tool never files a claim; the person files on the official site and signs it themselves.

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": {
      "company": "<company>"
    },
    "name": "find_breach_settlement"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNoOptional: the person's US state as a 2-letter code, when they mention it. Some settlements pay a state subclass more.
companyYesThe company or organization named on the breach letter or in the news, e.g. 'Columbia University', 'DaVita'. Nothing else about the person.
got_notice_letterNoOptional: true if they received a notice letter or email about the breach or the settlement, false if not.
had_out_of_pocket_lossesNoOptional: true if they paid money or lost time because of the breach (fraud, credit freeze fees, hours spent), false if not.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, and the description adds substantial context beyond them: data is read off the official court-authorized website, class definitions are verbatim, no PII is taken or stored, and the tool never executes a filing. It also discloses the fallback behavior when no settlement is open (reporting AG breach notices so the person keeps the letter).

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?

Front-loaded with user phrasings, then scope, then return contents, then the hard privacy and no-filing boundaries — a sensible order. The middle sentence enumerating every returned field is long and list-like, but nearly every clause carries decision-relevant information rather than filler.

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?

No output schema exists, so the description carries the full burden of describing returns, and it does so field by field: deadline and days left, payout types, verbatim class definition, whether the notice code is needed, case/court, official claim site, and a filled-in checklist link. The no-result case and privacy boundaries are also covered, leaving nothing an agent needs before calling it.

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 100%, so the schema already documents all four parameters, making 3 the baseline. The description still adds value by stressing that the company name is the only real input and that identifying details are neither required nor accepted, which prevents an agent from over-collecting data; it says nothing extra about the optional state or boolean flags beyond the schema.

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 and resource: it matches a company against open class-action data-breach and privacy settlements and returns the deadline, payout, class definition, court, and claim site. The five quoted user phrasings pin down exactly which requests this tool owns, and the final sentence rules out the adjacent act of filing a claim.

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?

Gives rich when-to-use triggers ('I got a data breach notice from X', 'is this settlement letter real') and a clear when-not ('This tool never files a claim'), plus the important input constraint that no SSN, notice ID, claim ID, or name is needed. It stops short of explicitly routing to the sibling tools (breach_settlement_details, list_open_breach_settlements), so an agent must infer that boundary.

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.