Skip to main content
Glama

Find open data breach settlements

open_settlements
Read-onlyIdempotent

US class action data breach settlements that are still taking claims, soonest deadline first, optionally for one company. Returns up to 5 with claim deadline, maximum payout per person, whether proof is needed, the official claim site and the Teollimi page.

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

Input Schema

NameRequiredDescriptionDefault
companyNoCompany name to filter by.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this a non-destructive, idempotent, closed-world read, so the safety profile is covered. The description adds genuinely new behavior: a hard cap of 5 results, deadline-ascending ordering, and no proof-of-claim filtering. It does not mention what happens with zero matches or whether results are cached, so it stops short of full transparency.

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?

Two dense sentences with zero padding: scope and ordering come first, the optional filter second, and the return fields last. Every clause carries information an agent would otherwise have to guess.

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?

There is no output schema, but the description compensates by enumerating the returned fields (deadline, max payout, proof requirement, claim site, Teollimi page) and the result cap. For a one-optional-parameter read tool, nothing material is missing.

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?

With a single parameter and 100% schema description coverage, the schema already documents 'company' fully. The description only restates that filtering is optional and scoped to one company, adding no format or matching semantics (e.g. partial vs exact name matching) 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?

The description names a specific resource ('US class action data breach settlements'), a precise scope ('still taking claims'), and a sort order ('soonest deadline first'), plus an optional filter. This distinguishes it from siblings like recent_breaches and search_breaches without needing to name them, since those are not constrained to open settlement claims.

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?

It implies when the tool is appropriate (open claims, optionally one company) and gives the ordering the caller can rely on, but it never states when to prefer it over search_breaches or recent_breaches, nor any exclusion. Usage is inferable rather than explicit.

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