Skip to main content
Glama

Lilambd Data for Agents

us-breach-notices

Which organisations notified US regulators of a data breach, when, and how many residents?. Official breach notices from US state attorney-general lists (CA, WA, OR, DE, more being added), HHS OCR and SEC 8-K Item 1.05, merged into one row per event across regulators. Facts and official links only; no breached data. Routes: /org (org*); /events (since, until, state, min_affected, org, limit); /coverage. Paid $0.01 USDC per call via x402 (_meta["x402/payment"]); set sample=true for a free 3-row preview.

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": {
      "route": "<route>"
    },
    "name": "us-breach-notices"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeYesOne of: /org, /events, /coverage. Replace {placeholders} with a value, e.g. /search or /HND.
paramsNoQuery parameters, e.g. {"q":"tokyo","limit":"50"}
sampleNoFree preview, max 3 rows

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and usefully discloses cost ($0.01 USDC per x402 call), a free sample preview, merged one-row-per-event behavior, and that only facts/official links (no breached data) are returned. It does not mention rate limits, authentication beyond payment, or explicit read-only status, so it is strong but not fully exhaustive.

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?

The description is dense but front-loaded: purpose, sources, merge logic, data limitation, routing, and payment/preview all appear without repetition. Every sentence or clause earns its place.

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?

For a paid, multi-route query tool with no output schema, the description supplies the missing context: sources, route mappings, payment model, and free preview. It does not define output row fields or filter defaults, leaving a small gap for an agent building a query.

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 3 is the baseline, but the description adds meaningful route-specific semantics—/org's org*, /events' since/until/state/min_affected/org/limit—that the generic route and params schema descriptions omit. It still does not clarify value types or defaults for those filters.

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 opening question states exactly what the tool returns—breach notifications, timing, and affected resident counts—and the named sources (state AG lists, HHS OCR, SEC 8-K) plus merge behavior make the resource unambiguous. No sibling tool covers this domain, so the specificity is enough to distinguish it.

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?

The 'Routes' section gives clear invocation guidance for /org, /events, and /coverage, and names the /events filters, which is the main usage decision. It lacks an explicit when-not-to-use or cross-tool alternative, but there is no competing breach-notice sibling to route to.

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