Skip to main content
Glama

Mallory

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. 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.

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.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the burden and largely does so: it discloses that results are lean summaries, the pagination envelope {items,total,offset,limit}, and a non-obvious constraint that timestamps support only __gte and __lt with no bare equality. It omits permissions, rate limits, and default sort behavior, which keeps it from a 5.

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?

Front-loaded with purpose and return shape, followed by the field/operator details that an agent actually needs at call time. It is dense, and the operator rules appear twice (also in the schema), which is mild redundancy but justified as a correctness guard.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six optional parameters, no annotations, and no output schema, the description covers all the gaps: item contents, pagination envelope, sortable fields, filter prefixes, and per-type operator rules. An agent can construct a correct filtered, sorted, paginated call and knows where to go for full detail.

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%, but the schema defers to the description for sort fields and filter prefixes ("see this tool's sort fields"), and the description supplies them: created_at/updated_at plus name:, uuid:, loss_type:, record_type:. It also enumerates operator support per type including the timestamp-only restriction. It does not explain how filter and fieldFilters interact or which field names are valid in filter beyond the listed prefixes.

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?

Opens with a specific verb+resource ("List and filter Mallory breaches") and immediately defines the return shape, so the agent knows the exact semantics. The closing pointer to getBreach for full detail clearly separates it from the sibling that fetches a single object.

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?

States the alternative explicitly: use getBreach when you need the full detail object, and use this tool for lean summary listing. It also specifies valid sort fields and filter prefixes, which directs correct invocation. It stops short of explicit exclusions such as when a text search should be done elsewhere, but the routing guidance is clear.

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