Skip to main content
Glama
Bosco Labs Data

Bosco Labs Data

Official

SEC EDGAR filings feed

search_sec_filings
Read-only

Retrieve SEC EDGAR filings by ticker, CIK, form type, 8-K item, or date to locate company reports, earnings releases, and market-wide filings with source links.

Instructions

SEC EDGAR filings of US-listed companies and other filers: any form (8-K, 10-K, 10-Q, S-1, 13D/13G, Form 4, DEF 14A, 20-F, ...), from filings accepted minutes ago back to 1994 (source: SEC EDGAR submissions API, indexes and live feed). Use it to find a company's latest reports, earnings release dates and times, officer changes or other 8-K events, or market-wide filings of one type.

Filter by tickers or CIKs (omit both for the whole market), form types, 8-K item codes or
earnings releases only. Filing date range: date_from/date_to, or the last `lookback_days`
days. Newest first.

Returns one row per filing: filing_date, accepted_at, market_timing (before_open,
market_hours, after_close), form, ticker, company_name, cik, items (8-K item codes),
item_descriptions, report_date and links: primary_document_url (the document; cite it),
filing_index_url.

Cost to the user: $0.001 per filing returned.

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

Input Schema

NameRequiredDescriptionDefault
ciksNo
date_toNo
tickersNo
date_fromNo
form_typesNoe.g. 8-K, 10-K, 10-Q, S-1, 13D, DEF 14A
max_resultsNoMax filings to return (1-100).
item_codes_8kNoOnly 8-Ks with these items, e.g. 5.02 (officer change), 1.01, 2.01
lookback_daysNoDays back when date_from is omitted; omit to get a company's latest filings of any date (tickers/CIKs) or the last 7 days (whole market)
earnings_releases_onlyNoOnly 8-K item 2.02 earnings releases

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.5

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, and the description adds real behavioral context beyond them: ordering (newest first), default window semantics (last 7 days for whole market, latest-any-date for a specific company), provenance (SEC submissions API, indexes, live feed back to 1994), and a per-filing cost of $0.001. The enumeration of return columns largely repeats the output schema, which slightly dilutes the added value.

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?

Three tight paragraphs with the core scope, then filtering, then output — front-loaded and scannable. The output-field paragraph spends several lines restating what the output schema already provides, which is the main slack.

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 nine-parameter, zero-required, open-world search tool, everything needed to call it correctly is present: scope, window defaults, market-wide fallback, filter interplay, ordering, and cost. An output schema already covers return values, so the field list is redundant rather than necessary, and the lack of sibling routing is the only substantive gap.

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?

With 56% schema coverage, the description compensates well at the cross-parameter level: it explains that tickers and CIKs are alternatives, that date_from/date_to and lookback_days are mutually substitutable windows, and that earnings_releases_only is shorthand for 8-K item 2.02. It does not mention max_results or characterize CIK/ticker format rules, but those are documented in 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 and resource ('SEC EDGAR filings of US-listed companies and other filers') and enumerates the covered form families (8-K, 10-K, 13D/13G, Form 4, etc.) plus the 1994-to-live time span, so the agent knows exactly what corpus is searched. It stops short of naming the overlapping sibling search_sec_insider_trades, leaving the boundary between 'any form' and a dedicated insider-trade feed to inference.

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?

Provides concrete scenarios ('latest reports, earnings release dates and times, officer changes or other 8-K events, or market-wide filings of one type') and states the key routing rule that omitting both tickers and CIKs returns the whole market. It gives no explicit when-not-to-use or pointer to an alternative tool, so the boundary with search_sec_insider_trades remains unstated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.