Skip to main content
Glama

Breach to Claim: data breach settlements

Open data-breach settlements taking claims, soonest deadline first

list_open_breach_settlements
Read-onlyIdempotent

Every open class-action data-breach (and privacy/tracking-pixel) settlement we have read off its official website, sorted by claim deadline: company, deadline and days left, the most cash it pays, whether receipts are needed, and the official site. Use for 'what data breach settlements can I claim right now', 'which settlements close this week', 'data breach settlements with no proof required'. Refreshed daily; each row says when its official site was last read.

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

Input Schema

NameRequiredDescriptionDefault
kindNodata_breach (default all) = stolen or exposed data; privacy_tracking = a website shared data through tracking pixels
limitNoHow many (default 20)
closing_within_daysNoOnly settlements whose claim deadline is within this many days
no_documents_optionNotrue = only settlements with a cash option that needs no receipts

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?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and repeatability are covered. The description still adds genuine context beyond them: results are deadline-sorted, refresh is daily, each row carries a last-read timestamp, and data is sourced from official settlement sites. It does not state whether results beyond the limit are reachable, which matters for a listing tool.

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 the resource and ordering, then the return fields, then usage examples, then freshness — a sensible order with little filler. The return-field enumeration and redundant restatement of deadline ordering are the only mild padding.

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?

No output schema exists, so the description carries the return-value burden, and it does so by listing the row fields and the freshness timestamp. Coverage limits (only settlements read from official sites) and ordering are disclosed, though pagination behavior and empty-result semantics are left implicit for a filtered-list tool.

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 four parameters (kind enum, limit, closing_within_days, no_documents_option) are already documented, making the baseline 3. The example queries loosely map onto closing_within_days and no_documents_option, which adds a little interpretive help but no syntax or edge-case detail beyond the schema.

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?

Names a specific verb and resource with scope and ordering: "Every open class-action data-breach ... settlement ... sorted by claim deadline", then enumerates the returned fields (company, deadline, days left, cash, receipts, official site). It does not name or contrast with the sibling tools find_breach_settlement or breach_settlement_details, so it stops short of a 5.

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?

Three concrete example user questions ("what data breach settlements can I claim right now", "which settlements close this week", "with no proof required") give an agent a clear sense of when this tool fires. It stops short of exclusions or pointing to the details/search siblings when a specific settlement is already known.

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.