Skip to main content
Glama

Search data breaches by company

search_breaches
Read-onlyIdempotent

Find publicly reported data breaches of a company or service by name (any language, e.g. Coupang, 쿠팡, SK Telecom, Ticketmaster, アスクル). Returns up to 5 most recent incidents with date, number affected, leaked data types, compensation and fine flags, a source link and the Teollimi page, plus how many incidents match in total.

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": {
      "query": "<query>"
    },
    "name": "search_breaches"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: ko (Korean), en (English) or ja (Japanese). Defaults to the query's language, else English.
queryYesCompany or service name.

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 cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the description adds value by disclosing the result cap of 5, recency ordering, and the presence of a total-match count. It stops short of saying what happens when zero incidents match or whether the cap is adjustable.

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?

Two sentences, front-loaded with purpose and then the return payload; nothing is redundant. The second sentence is dense with an enumerated field list, but each item tells the agent something it would otherwise have to guess without an output schema.

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 carries the burden of describing returns, and it does so thoroughly (date, affected count, data types, compensation/fine flags, source link, Teollimi page, total count). Remaining gaps are minor: empty-result behavior and whether results are ordered strictly by date.

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 the baseline is 3; the description earns an extra point by clarifying that the query accepts names in any language and by demonstrating Korean, Japanese and English forms. It does not explain the lang parameter's fallback behavior, which the schema already handles.

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 — 'find publicly reported data breaches of a company or service by name' — plus concrete multilingual examples (Coupang, 쿠팡, Ticketmaster). The company-name lookup scope is clearly distinguishable from a generic 'recent breaches' listing.

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: use it when you have a company or service name and want its breach history. There is no explicit when-not guidance, no mention of what to do without a name, and no named alternative (e.g. recent_breaches) for the browse-recently case.

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