Skip to main content
Glama

Sec Enforcement Actions

sec_enforcement_actions
Read-onlyIdempotent

SEC enforcement actions by type: litigation releases (civil actions filed in federal court), administrative proceedings (in-house actions before an ALJ or the Commission), or trading suspensions. Answers 'recent SEC litigation releases', 'SEC administrative proceedings', 'what trading suspensions has the SEC issued'. The distinction matters, an administrative proceeding is not a federal-court lawsuit. Returns dated items with links. Covers only the current feed window (about 25 items per type), not history.

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": {
      "type": "litigation"
    },
    "name": "sec_enforcement_actions"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoWhich SEC action type to return (default litigation).
limitNoHow many items to return, 1-25 (default 25).

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, idempotent behavior, but the description adds genuinely useful context beyond them: it discloses the feed window ceiling (~25 items per type), that history is not covered, and that results are dated items with links. It does not mention rate limits or auth, but nothing in the annotations contradicts the described read-only, non-destructive behavior.

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?

Scope and type distinctions come first, followed by the sample questions and then the coverage caveat, so the important routing information is front-loaded. The quoted example questions are slightly redundant with the type explanations, but each sentence carries weight and there is no filler.

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

Completeness4/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 compensates by stating that dated items with links are returned, and it flags the feed-window limit so the agent knows not to promise historical coverage. A little more on what a returned item contains would fully close the gap for a no-output-schema tool.

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%, so defaults and the 1-25 limit range are already documented. The description still adds value by explaining what each enum value actually denotes in legal terms, which goes beyond the bare enum labels. It does not add syntax or formatting guidance, which keeps it below a 5.

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?

Names a specific resource (SEC enforcement actions) and enumerates the three action types, explaining what each means: litigation releases are civil actions in federal court, administrative proceedings are in-house before an ALJ or the Commission, trading suspensions are distinct. An agent can distinguish this from a generic enforcement tool without opening the 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 clear when-to-use signal via sample questions ('recent SEC litigation releases', 'what trading suspensions has the SEC issued') and an explicit scope limitation ('covers only the current feed window, not history'). It does not name a sibling alternative such as a historical or full-text enforcement search, so the alternative routing is left implicit.

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.