Skip to main content
Glama

Enforcement Search

enforcement_search
Read-onlyIdempotent

Search US federal enforcement actions against a company, person or topic by name, DOJ criminal charges, guilty pleas, settlements, indictments and civil resolutions. Answers 'what has DOJ charged Binance with', 'enforcement actions against Purdue Pharma', 'DOJ settlement opioid', 'who was indicted for FTX'. Returns dated actions newest-first with a link to the official release, the DOJ components involved (e.g. Antitrust Division, Criminal Division) and a summary. Searches DOJ press releases (~270,000 back to 2009), the SEC feeds are recent-window only and are NOT searchable, so use enforcement_recent for those.

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": "Binance"
    },
    "name": "enforcement_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many actions to return, 1-50 (default 20), newest first.
queryYesCompany, person or topic name, e.g. "Binance", "Purdue", "opioid", "price fixing". Matched against the release TITLE.
sinceNoOnly actions on or after this date (YYYY-MM-DD). Applied after fetching, since the DOJ API ignores date filters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"How many actions to return, 1–50 (default 20), newest first."New value: +"How many actions to return, 1-50 (default 20), newest first."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, idempotent and open-world, so the lower bar applies; the description still adds real substance — corpus size (~270,000 releases since 2009), result ordering, and the returned fields (dated action, official link, DOJ components, summary) in the absence of an output schema. The caveat that SEC feeds are not searchable here is behavior no annotation conveys. It does not mention rate limits or result-count ceilings beyond the schema's limit.

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 verb and corpus, then the routing exclusion — good ordering. The run of quoted example questions is slightly verbose and duplicates intent already implied by the query parameter, but each sentence carries usable information.

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 no output schema, the description supplies the return shape, ordering and per-result fields, plus the corpus boundary and an explicit alternative for the uncovered SEC data. Nothing an agent needs in order to call this correctly is missing.

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 description coverage is 100%, so the baseline of 3 applies. The description adds conceptual framing (query means company, person or topic; coverage of charges, pleas, settlements, indictments) but no syntax or format detail beyond what the schema already states for query, limit and since.

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 (Search) and resource (US federal enforcement actions) plus the exact corpus searched (DOJ press releases back to 2009). It also names what it is not — SEC feeds are excluded — so an agent can separate it from enforcement_recent without opening a schema.

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 the agent: SEC feeds are 'recent-window only and are NOT searchable, so use enforcement_recent for those', while this tool covers the historical DOJ corpus. The embedded example questions ('what has DOJ charged Binance with', 'who was indicted for FTX') give concrete triggering contexts.

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.