Skip to main content
Glama

Enforcement Recent

enforcement_recent
Read-onlyIdempotent

Recent US federal enforcement actions across DOJ and the SEC, newest first, the 'what has been brought lately' view. Answers 'recent SEC enforcement actions', 'latest DOJ prosecutions', 'new securities fraud cases this week'. Merges DOJ press releases with SEC litigation releases, administrative proceedings and trading suspensions, each item dated and linked to the official source. Use enforcement_search to look up a specific company or topic by name.

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": {},
    "name": "enforcement_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many actions to return, 1-100 (default 25).
sourceNoLimit to one agency: "doj", "sec", or "all" (default).

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–100 (default 25)."New value: +"How many actions to return, 1-100 (default 25)."
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real context beyond that: which sources are merged (DOJ press releases, SEC litigation releases, administrative proceedings, trading suspensions) and that each item is dated and linked to the official source. It does not discuss result caps or freshness lag, which keeps it below 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.

Conciseness5/5

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

Front-loaded with resource, scope and ordering; then query examples; then source composition; then the sibling routing. No sentence is redundant and the alternative is placed last where a reader needs it.

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 two-optional-parameter list tool with no output schema, the description covers scope, ordering, source composition, item shape (dated and linked) and the sibling boundary. Nothing an agent needs to invoke it correctly is missing.

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% with both parameters documented and an enum for source, so baseline would be 3. The description earns an extra point by explaining what the 'source' dimension actually draws from — DOJ press releases versus SEC litigation releases, admin proceedings and trading suspensions — which the enum values alone don't convey.

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 resource (recent US federal enforcement actions), the agencies covered (DOJ and SEC), and the ordering (newest first). The final sentence explicitly separates it from enforcement_search, so an agent can pick between them 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 Guidelines5/5

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

Gives concrete trigger queries ('recent SEC enforcement actions', 'latest DOJ prosecutions', 'new securities fraud cases this week') and names the alternative tool with the condition that selects it (specific company or topic by name). Explicit when-to-use and when-to-use-something-else.

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.