Skip to main content
Glama

Companies Daily – SEC filings of US companies

Daily edition of SEC filings

get_daily_edition
Read-onlyIdempotent

What US companies filed with the SEC on one EDGAR business day: companies by event type and full lists of bankruptcies, revocations, debt defaults, delisting notices, late filings and restatements. Without a date: the latest ready edition.

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

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD (days: list_editions).

Output Schema

NameRequiredDescriptionDefault
urlYes
as_ofNo
attributionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real behavioral context beyond that: the resource is scoped to a single EDGAR business day and defaults to the latest ready edition when no date is given. It does not discuss volume, size, or pagination of the returned lists.

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?

Two dense sentences, front-loaded with the core resource and scope, then the default behavior. Every clause earns its place by naming the actual event categories the agent will receive.

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 an output schema present, return-value detail is unnecessary, and annotations cover the safety profile. For a one-optional-parameter read tool, the description supplies scope, content composition, and default behavior — everything an agent needs to invoke it correctly.

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% and the single optional date parameter is fully specified with a YYYY-MM-DD pattern and a pointer to list_editions. The description still adds meaning the schema does not: what happens semantically when the parameter is omitted, namely returning the latest ready edition.

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 and resource — what US companies filed with the SEC on one EDGAR business day — and enumerates the concrete contents (bankruptcies, revocations, debt defaults, delisting notices, late filings, restatements). This is specific enough that an agent can distinguish a daily-edition digest from the event-listing and company-lookup siblings.

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?

The description gives clear contextual guidance: supply a date to target a specific EDGAR business day, or omit it to get the latest ready edition. It does not explicitly name alternatives or exclusions (e.g., when to prefer list_events or list_editions), so it falls short of full when/when-not guidance.

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