Skip to main content
Glama

List recent data breaches

recent_breaches
Read-onlyIdempotent

Data breaches announced in the last few days (default 30), newest first, optionally in one country. Returns up to 10 incidents with date, scale, leaked data types, a source link 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": "recent_breaches"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back to look (1-60, default 30).
langNoAnswer language: ko (Korean), en (English) or ja (Japanese). Defaults to the query's language, else English.
limitNoNumber of incidents (1-10, default 10).
countryNoISO 3166-1 alpha-2 country code, e.g. KR, US, JP.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real behavior beyond that: the sort order, the hard cap of 10 incidents, and the exact fields returned (date, scale, leaked data types, source link, Teollimi page), which is exactly the sort of context annotations cannot supply.

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 tight sentences with no filler; the recency window and ordering come first, followed by the return shape. Every clause carries information an agent needs.

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?

With no output schema, the description correctly compensates by enumerating the returned fields, and annotations cover the safety profile. Minor gaps remain: no mention of behavior when zero breaches match, and no guidance on the language parameter's effect on returned content versus query language.

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 are already documented with types, ranges and defaults. The description reinforces the days default (30) and the limit ceiling (10) but adds nothing about lang or the country code format. Baseline 3 is appropriate when the schema carries the load.

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?

States a specific verb+resource ('Data breaches announced in the last few days'), plus scope qualifiers: default 30-day window, newest-first ordering, optional country filter, up to 10 results. This lets an agent tell it apart from a general search tool, though it never names the sibling (search_breaches) that would be the alternative for non-recency queries.

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?

Usage is implied by the recency framing and the 'optionally in one country' clause, giving a reasonable sense of when the tool fits. There is no explicit when-not or named alternative, so an agent must infer that targeted lookups belong to search_breaches.

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