Skip to main content
Glama

Breach to Claim: data breach settlements

One breach settlement: class definition, every benefit, every date, official site

breach_settlement_details
Read-onlyIdempotent

Everything read off one settlement's official website: the class definition and any subclasses verbatim, each benefit with its cap and whether documents are needed, the claim, opt-out and objection deadlines, the final approval hearing, the fund and class size when stated, the case, court, administrator and its contact, and the source page for each. Pass the slug from find_breach_settlement or list_open_breach_settlements.

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": {
      "slug": "<slug>"
    },
    "name": "breach_settlement_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe settlement's slug, e.g. 'columbia-university'
got_notice_letterNoOptional, as in find_breach_settlement
had_out_of_pocket_lossesNoOptional, as in find_breach_settlement

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety and idempotency are covered. The description adds genuine value by disclosing provenance ('the source page for each') and that some fields are conditional ('when stated', 'any subclasses'), signalling partial results. However, it says nothing about behavior on an invalid or unknown slug, latency, caching, or whether repeated calls reflect site updates — modest gaps for an open-world fetch.

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?

One front-loaded sentence opens with the scope ('one settlement's official website') and then lists contents in a dense, parallel enumeration with a closing instruction on the slug. Nothing is redundant, though the single run-on sentence packs a dozen clauses and would scan faster as a short list.

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 return-shape burden entirely — and it enumerates the returned fields in detail, including per-field provenance. For a read-only single-record fetch with fully described parameters, nothing an agent needs in order to call it correctly is missing.

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?

With 100% schema coverage the schema already documents all three parameters, so the baseline is 3. The description goes slightly further by naming the sibling tools that produce a valid slug value, reinforcing what the string should contain, but it defers entirely to the schema for the two optional booleans ('as in find_breach_settlement'), adding no semantics of its own for those.

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 ('Everything read off one settlement's official website') and enumerates the exact contents: class definition, subclasses verbatim, benefits with caps and document requirements, three deadline types, fund and class size, case/court/administrator, and source page. This is clearly distinguishable from the sibling list/search tools, which return settlement candidates rather than one settlement's full record.

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?

Explicitly routes the agent: 'Pass the slug from find_breach_settlement or list_open_breach_settlements,' which establishes the required two-step workflow and names the alternatives. It lacks an explicit when-not-to-use statement (e.g., don't call before you have a slug, or how it differs if a settlement is closed), but the sequencing guidance is clear.

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.