Skip to main content
Glama

listBreaches

List and filter Mallory breaches, returning lean summaries as {items,total,offset,limit}. Each item includes: name, description, affected organizations, record_type and loss_type, affected record counts, associated threat actors/malware/attack-patterns, and dates. Filter prefixes: name:, uuid:, loss_type:, record_type:. Sort by created_at, updated_at. For breaches linked to organizations currently matched to tenant assets, set fieldFilters matched_asset_count__gt to "0". Match age is irrelevant; use created_at for newly recorded breaches. Association does not establish victim status: verify that a matched organization is the victim. Field operators append to a field name with __: strings support __neq, __in, __not_in, __like, __ilike; numbers support __gt, __gte, __lt, __lte. Timestamps (created_at, updated_at) support __gte and __lt ONLY — there is no __gt, __lte, or bare equality on them, so express a range as the half-open created_at__gte=&created_at__lt=. Pass an item's identifier to getBreach for the full detail object.

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

Input Schema

NameRequiredDescriptionDefault
sortNoField to sort by (see this tool's sort fields).
limitNoMax items to return (1-100, default 25).
orderNoSort order (default: desc).
filterNoPrefix filter string (see this tool's filter prefixes). No prefix = default name/text search.
offsetNoItems to skip, for pagination.
fieldFiltersNoAdvanced structured filters as a map of query-param name -> value. Use a bare field for exact match, or a field__operator key for ranges/sets. Field operators append to a field name with `__`: strings support __neq, __in, __not_in, __like, __ilike; numbers support __gt, __gte, __lt, __lte. Timestamps (created_at, updated_at) support __gte and __lt ONLY — there is no __gt, __lte, or bare equality on them, so express a range as the half-open created_at__gte=<start>&created_at__lt=<end>.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, yet the description discloses the lean-summary return contract, the filter/sort vocabulary, half-open timestamp range semantics with explicit exclusions (no __gt, __lte, or bare equality), and the victim-status caveat. It does not state auth requirements or rate limits, but the operational semantics are unusually well disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense and front-loaded with the return shape first, but the __ operator paragraph is duplicated verbatim between the description and the fieldFilters schema, and the filter-prefix versus fieldFilters distinction is left implicit across a long block. Several clauses could be tightened without losing content.

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?

Covers the list contract, filtering, sorting, pagination, tenant-asset matching, and the handoff to getBreach for full records. Missing only an explicit statement that the victim-verification caveat implies downstream checks, and any note on result limits beyond the schema's maximum of 100.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds substantial meaning beyond the 100%-covered schema: the four filter prefixes (name:, uuid:, loss_type:, record_type:), the sortable fields (created_at, updated_at), and a concrete fieldFilters example. The __ operator rules are repeated from the schema but the prefix convention is new information the schema only refers to vaguely.

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 (list and filter Mallory breaches) plus the exact return shape {items,total,offset,limit} and enumerated item fields. This clearly distinguishes it from getBreach, whose role is explained at the end.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes to getBreach for full detail objects, tells the agent to set matched_asset_count__gt to "0" for tenant-matched organizations, and warns that a matched organization is not necessarily the victim. It even notes match age is irrelevant and to use created_at for newly recorded 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