Skip to main content
Glama

beatandraise.com SEC Filings

List Filings

get_filings
Read-onlyIdempotent

Query SEC filings by form type, date range, CIK and/or 8-K item.

Returns deduplicated filing metadata sorted by filing date (newest first). Each filing's content_object lists its documents (filename, doc_type, description, sequence; sequence 1 is the primary document); read any of them with get_document(cik, accession_number, filename). A document's link, to cite, is beatandraise_base_url + filename (the beatandraise.com viewer); the filing's own source gives the primary document's link and a ready-made citation. Each filing also carries its items (an 8-K's, e.g. "2.02 Results of Operations and Financial Condition") when it has any. The R*.htm files are XBRL financial-table pages; list_filing_tables says which table each one is.

An 8-K carries a headline when its press release (EX-99.1) has one, e.g. "Tesla Third Quarter 2026 Production, Deliveries & Deployments": read from the release's opening lines by rules, so use it to choose which 8-K to read, not as a quotation (about 2% are another line of the release; verify_quote before quoting). No headline says nothing about the filing: its exhibit may be a deck or an agreement, or it may have no EX-99. An 8-K whose only item is 9.01 and that has no headline files exhibits and nothing else: exhibits_only lists them by type and the SEC's exhibit title ("EX-5.01 Opinion re legality; EX-99.01 Additional exhibits (no press release headline)"), so it holds no financial statements despite its item's name, and is rarely worth reading for news.

Args: form: SEC form type (e.g. "10-K", "10-Q", "8-K", "4", "13F-HR", "S-1"), or several comma-separated in one call (up to 20), e.g. "N-CSR,N-CSRS,N-CSR/A,N-CSRS/A" or "10-K,10-K/A". Amendments are their own form types, so name them to include them. cik: Company CIK (e.g. "0000320193" or "320193") from_date: Start date inclusive (YYYY-MM-DD). Without cik, defaults to 30 days before to_date (or today); pass it to reach older filings. to_date: End date inclusive (YYYY-MM-DD) limit: Max results (1-100, default 100; at most 25 with include_item_text). For more, page with offset offset: Pagination offset item: Only 8-Ks reporting this item, by its number as the 8-K header states it, e.g. "5.02" (departure or election of directors or officers, officers' pay), "1.01" (material agreement), "2.01" (acquisition or disposal), "4.01" (auditor change), "5.07" (shareholder vote); several comma-separated match any ("1.01,2.01"). Defaults form to "8-K,8-K/A". Numbered since 2004-08-23. Use it instead of reading 8-Ks one by one to find, say, every director change this week. include_item_text: With item, also return each filing's text of that item (item_texts: item, title, text up to 10,000 characters, highlight_url marking it in the filing), so a screen across companies takes one call. The header only says 5.02; whether it is a director, a CEO or a pay plan is in the text. item_text: Items whose text to return with each filing, for any 10-K, 10-Q or 8-K (not only with item): by number or name, up to 5 comma-separated, e.g. "MD&A", "1A", "Risk Factors", "Part II Item 1A", "5.02". With form="10-Q" and a cik, "MD&A" gives a company's last several MD&As in one call. A filing without that Item says so in its item_texts entry ("not in this filing"). item_text_chars: Characters of text per Item, 1,000-100,000 (default 10,000). The whole page carries at most 500,000 characters of text, so limit is lowered to fit: ask for fewer filings when you want whole MD&As.

Input Schema

NameRequiredDescriptionDefault
cikNo
formNo
itemNo
limitNo
offsetNo
to_dateNo
from_dateNo
item_textNo
item_text_charsNo
include_item_textNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, and the description adds substantial non-obvious behavior: dedup plus newest-first ordering, the ~2% unreliable headline cases with a verify_quote warning, the exhibits-only 8-K caveat, and a 500,000-character page cap that silently lowers limit. These are exactly the traits structured fields cannot convey.

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?

Front-loaded with purpose and return shape, then args, which is the right order, and the length is defensible for ten undocumented parameters. Still, some passages are heavier than needed, such as the long worked headline example and the EX-5.01 exhibit-title sample, which could be trimmed without losing guidance.

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?

Covers everything an agent needs to call this correctly: what is returned, how documents/items/headlines are represented, citation construction, pagination, and each parameter's semantics. An output schema exists, so the extra return-value detail is bonus rather than filler.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does: it documents all ten parameters with formats, examples, defaults, bounds (limit 1-100, 25 with include_item_text; item_text_chars 1,000-100,000), enum-like value lists for item, and the interaction between item/include_item_text/item_text and form.

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?

Opens with a specific verb+resource and scope: 'Query SEC filings by form type, date range, CIK and/or 8-K item,' and immediately states the return shape ('deduplicated filing metadata sorted by filing date'). It also routes to the right follow-up tools (get_document, list_filing_tables), so an agent knows exactly what this call produces versus a detail/document fetch.

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 concrete when-to-use guidance for the tricky parameters ('Use it instead of reading 8-Ks one by one to find every director change this week') and when to include item text. It also explains default behavior for from_date and item. It never explicitly contrasts with the sibling search_filings, which is the one likely confusion point left unaddressed.

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