Skip to main content
Glama

Recent enforcement items from the regulators' own feeds

enforcement_actions
Read-only

Recent enforcement items from the regulators' own feeds: SEC litigation releases and administrative proceedings, CFPB enforcement actions, FTC consumer-protection and competition press releases, DOJ press releases. Each: agency, feed, title, date, link, a short summary and, for SEC and CFPB, the respondent named in the title. Filters: agency, words (q), days (1-90). The feeds hold the latest 25-30 items each. Price: $0.003 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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

Input Schema

NameRequiredDescriptionDefault
qNoWords that must appear in the title or summary (optional)
daysNoLook back this many days, 1 to 90, default 30
limitNoItems to return, 1 to 50, default 20
agencyNosec, cfpb, ftc or doj; omit for all

Output Schema

NameRequiredDescriptionDefault
countNo
itemsNo
sinceNo
sourceNo
agenciesNo
checkedAtNo
disclaimerNo
feedsUnavailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / feedsUnavailable
      Added value: +{}
    • addedOutput schema / properties / since
      Added value: +{}
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the read-only/open-world annotations, the description discloses important behavior: each feed holds only the latest 25-30 items, results include specific fields, and calls cost $0.003 via x402 with failures not charged. It also makes clear the respondent field is limited to SEC and CFPB items.

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

Conciseness5/5

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

The description is front-loaded and dense with useful information, using colon-separated lists for sources and fields. Every element contributes to understanding the data, filters, coverage limits, or pricing.

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?

For a read-only aggregation tool with full schema coverage, annotations, and an output schema, the description supplies the remaining essential context: source coverage, feed recency limits, fields, filters, and payment behavior. No critical invocation detail appears to be 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 parameter meaning is already well documented. The description mentions agency, q, and days but does not add material semantics beyond the schema, and it omits the limit parameter.

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?

The description states exactly what the tool returns: recent enforcement items from named regulator feeds, with SEC, CFPB, FTC, and DOJ sources and item fields enumerated. This clearly distinguishes it from generic news/feed siblings by domain and regulatory source.

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 filters imply how the tool can be narrowed by agency, words, and days, but the description does not explicitly say when to use this tool instead of alternatives or when not to use it. Usage is inferable but not directly guided.

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