Skip to main content
Glama

mkts Market Data

Get company filings

get_filings
Read-onlyIdempotent

List recent SEC filings for a US-listed company or fund, newest first, from SEC EDGAR. Each filing has its date, form type, a plain-language title (for 8-Ks, the events reported), the period it covers, and links to the EDGAR index page and the main document. Use to find the latest 10-K, 10-Q or 8-K, or to see what a company has filed recently. Insider-ownership forms (3, 4, 5, 144) are not included. A fund trust files for all its funds together; sharedFiler in the result marks this, and some filings may concern sibling funds.

Input Schema

NameRequiredDescriptionDefault
typeNoOnly filings of this exact SEC form type, e.g. 10-K (annual report), 10-Q (quarterly report), 8-K (current report), DEF 14A (proxy statement). Omit for all types.
limitNoMaximum filings to return, newest first.
symbolYesUS ticker of a stock or ETF, e.g. NVDA, BRK-B, SPY.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum filings to return, newest first."
    • addedInput schema / properties / symbol / description
      Added value: +"US ticker of a stock or ETF, e.g. NVDA, BRK-B, SPY."
    • changedInput schema / properties / type / description
      Previous value: -"Optional filing type such as 10-K, 10-Q, or 8-K."New value: +"Only filings of this exact SEC form type, e.g. 10-K (annual report), 10-Q (quarterly report), 8-K (current report), DEF 14A (proxy statement). Omit for all types."
  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 establish that this is a safe, read-only, idempotent, open-world operation. The description adds useful behavioral context beyond annotations: results are newest first, include specific fields and links, exclude insider-ownership forms, and flag shared fund filers with sharedFiler.

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?

The description is front-loaded and efficient: purpose first, then return contents, use cases, exclusions, and a fund-specific caveat. Each sentence contributes actionable information without repetition.

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?

For a three-parameter read-only filings lookup with no output schema, the description explains what is returned, ordering, exclusions, and a non-obvious fund-trust behavior. Together with annotations and a fully documented schema, an agent has enough context to call it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so the input schema already documents symbol, type, and limit thoroughly, including examples and the 'omit for all types' behavior. The description adds little parameter-level meaning beyond what the schema provides, making the baseline score appropriate.

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?

The description states a specific verb and resource: list recent SEC filings for a US-listed company or fund from SEC EDGAR. It distinguishes the tool from sibling market-data tools by focusing on regulatory filings and gives concrete examples such as 10-K, 10-Q, and 8-K.

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?

It clearly says to use this tool to find the latest 10-K, 10-Q, or 8-K, or to see recent filings, and explicitly excludes insider-ownership forms 3, 4, 5, and 144. It does not name a sibling alternative, but there is no obvious competing filing tool in the provided sibling list.

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