Skip to main content
Glama

Ftc Search Cases

ftc_search_cases
Read-onlyIdempotent

Search FTC (Federal Trade Commission) enforcement cases and proceedings by company name, individual name, case/matter number, or keyword, with optional date range, merger-vs-non-merger filter, and case-status filter. Covers both competition (antitrust/merger) and consumer-protection enforcement, complaints, consent orders, settlements, and federal-court actions. Returns each matching case's title, FTC slug (pass to ftc_case_detail for documents), type of action, case status, and last-updated date. Example: ftc_search_cases({ query: "Kroger", category: "merger" }).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "Kroger"
    },
    "name": "ftc_search_cases"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax cases to return, newest-updated first. Default 20, max 100.
queryNoCompany name, individual name, case/matter number, or keyword. Omit to browse all cases (combine with category/status/dates).
statusNoRestrict to cases in this status. Omit for any status.
categoryNoRestrict to merger enforcement, non-merger (conduct) enforcement, or both ("any", the default).
end_dateNoLatest "last updated" date to include, YYYY-MM-DD.
start_dateNoEarliest "last updated" date to include, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the date filters act on the case's last-updated date rather than filing date, results are ordered newest-updated first, and the exact fields returned are enumerated. No rate limits or pagination behavior beyond 'limit' are mentioned, 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 the core action and filters, then coverage, then return fields, then a compact example call — a sensible ordering. The enumeration of action types ('complaints, consent orders, settlements, and federal-court actions') is somewhat listy and overlaps the coverage sentence, but the total length is justified for a six-parameter search tool.

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?

There is no output schema, so the description bears the burden of describing returns, and it does: title, FTC slug, type of action, case status, and last-updated date. Combined with the 100% schema coverage and the annotations, an agent has everything needed to call this correctly and to chain into ftc_case_detail.

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 schema already carries the meaning of all six parameters including enums and defaults. The description restates the filter set (date range, merger-vs-non-merger, status) and clarifies that dates bound the last-updated field, but adds no syntax or edge-case detail the schema lacks. Baseline 3 is appropriate.

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 ('Search FTC enforcement cases and proceedings') plus the searchable dimensions (company, individual, case number, keyword) and the coverage scope (competition and consumer-protection, complaints through federal-court actions). It also names the sibling it hands off to ('pass to ftc_case_detail for documents'), so an agent can separate the two tools without opening either schema.

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?

Gives a concrete when-to-use path: query matches by name/number/keyword, and the description explicitly supports browsing by combining filters. Routing to ftc_case_detail for documents is an explicit alternative-plus-condition. It does not, however, address when to prefer other siblings such as ftc_recent_actions or company_register_search, so it stops short of full exclusion guidance.

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.