Skip to main content
Glama

What to do after a data breach

breach_response_steps
Read-onlyIdempotent

Steps to take after a breach notice, by the kinds of data that leaked (password, card, national ID and so on), with official places to check exposure or get help in Korea, the US and Japan.

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

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: ko (Korean), en (English) or ja (Japanese). Defaults to the query's language, else English.
leakedNoKinds of data that leaked, from the breach notice.
countryNoWhere the person lives, for the official services (default from lang).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnly/idempotent/non-destructive and closed-world, so the safety profile is covered. The description adds the important scoping fact that official resources are limited to Korea, the US and Japan, which tells an agent the answer will be jurisdiction-bound. It does not state whether the guidance is static reference content or fetched live, which matters for an advisory tool.

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?

A single dense sentence that front-loads the purpose and then qualifies scope by data type and jurisdiction. Nothing is wasted, though the jurisdiction list is packed into a trailing clause rather than given its own emphasis.

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 3-parameter, fully documented, read-only advisory tool with no output schema, the description covers what the tool produces conceptually (steps plus official resources) and its geographic limits. Only the return shape and whether results are static versus live remain unstated, which is a minor gap.

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 coverage is 100%, so the enum meanings and defaults are already documented. The description reinforces that 'leaked' corresponds to data types listed in the breach notice and that 'country' drives which official services are returned, but adds no format or validation detail beyond the schema.

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?

The description names the resource concretely: post-breach action steps segmented by leaked data type, backed by official exposure-check/help resources in KR, US and JP. That is distinguishable from the sibling lookup tools (search_breaches, recent_breaches), though no sibling is named explicitly.

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?

The trigger condition is implied well — 'after a breach notice' — so an agent knows the situation that selects this tool. However there is no explicit when-not guidance and no mention of the alternative hint tools for looking up the breach itself rather than the remediation steps.

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