Skip to main content
Glama

Companies Daily – SEC filings of US companies

SEC filing events with filters

list_events
Read-onlyIdempotent

Classified SEC filings of US companies (bankruptcies, debt defaults, delisting notices, late filings, restatements, leadership changes, IPOs, Form D raises, annual and quarterly reports…) filtered by type, day or date range and state; newest first, with paging. Each item: dates, type, form, 8-K items, detail, amount, link to the filing on EDGAR, company and url of its page.

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

Input Schema

NameRequiredDescriptionDefault
toNoTo this day.
dateNoOne EDGAR business day (edition date).
fromNoFrom this day.
typeNoEvent type (list_event_types).
limitNo
stateNoState of the business address: slug ("california") or USPS code ("CA").
offsetNo

Output Schema

NameRequiredDescriptionDefault
totalYes
eventsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: results are ordered newest first, paging is supported, and each item carries a link to EDGAR plus a company page URL. No contradictions with the annotations.

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?

Two sentences, front-loaded with the resource and scope, followed by filtering and result shape. The long parenthetical list of event types is somewhat verbose given the enum already exists in the schema, but it is the only real padding.

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?

For a read-only filtered-list tool with 7 optional parameters, full annotations and an output schema, the description covers what the tool returns and how to narrow it. Re-listing per-item fields is slightly redundant with the output schema, but nothing an agent needs to call 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 71%, so the baseline is around 3; the description goes beyond it by mapping the filter axes to the parameters ("by type, day or date range and state") and hinting at limit/offset via "with paging". It does not clarify the mutually-exclusive semantics of date vs from/to, which is the main remaining ambiguity left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: "Classified SEC filings of US companies" with an explicit enumeration of event categories and the filter axes. An agent can tell this is the event-listing tool, though it never names a sibling (e.g. list_editions or get_daily_edition) to disambiguate overlapping listing tools.

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?

Usage is implied by the described filter modes (type, single day vs date range, state), so an agent can infer how to query. However, there is no explicit when-to-use/when-not guidance and no routing between this tool and siblings like list_editions or get_daily_edition, which also surface filing data.

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