Skip to main content
Glama

Get Company Filings

get_company_filings
Read-onlyIdempotent

Get recent SEC filings for a company by CIK number, ticker, or company name. Returns filing dates, form types, and accession numbers. Optionally filter by form type (e.g., "10-K", "10-Q", "8-K"). Response field matched_by says whether the company was matched by ticker or by company name.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cik": "320193"
    },
    "name": "get_company_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikYesCompany CIK ("320193"), ticker ("AAPL"), or name ("Apple") — ticker/name are auto-resolved to a CIK
form_typeNoFilter by SEC form type (e.g., "10-K", "10-Q", "8-K", "DEF 14A"). Omit to return all recent filings.

Output Schema

NameRequiredDescriptionDefault
cikYesCompany CIK number
filingsYesRecent SEC filings (up to 20 results)
matched_byNoHow the company was matched: ticker, cik or company_name
company_nameYesOfficial company name from SEC
fiscal_year_endYesCompany's fiscal year end date (MMDD format)
sic_descriptionYesSEC SIC industry classification description
filter_form_typeYesForm type filter applied ('all' if none specified)
state_of_incorporationYesState where company is incorporated

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / matched_by
      Added value: +{
      +  "description": "How the company was matched: ticker, cik or company_name",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / cik / description
      Previous value: -"Company CIK number (digits only, e.g., \"320193\" for Apple)"New value: +"Company CIK (\"320193\"), ticker (\"AAPL\"), or name (\"Apple\") — ticker/name are auto-resolved to a CIK"
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "cik": {
      +      "description": "Company CIK number",
      +      "type": "string"
      +    },
      +    "company_name": {
      +      "description": "Official company name from SEC",
      +      "type": "string"
      +    },
      +    "filings": {
      +      "description": "Recent SEC filings (up to 20 results)",
      +      "items": {
      +        "properties": {
      +          "accession_number": {
      +            "description": "SEC accession number for the filing",
      +            "type": "string"
      +          },
      +          "document_url": {
      +            "description": "Full URL to the primary document on SEC website",
      +            "type": "string"
      +          },
      +          "filing_date": {
      +            "description": "Date filing was submitted to SEC (YYYY-MM-DD)",
      +            "type": "string"
      +          },
      +          "form": {
      +            "description": "SEC form type (e.g., 10-K, 10-Q, 8-K)",
      +            "type": "string"
      +          },
      +          "primary_document": {
      +            "description": "Primary document filename",
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "accession_number",
      +          "filing_date",
      +          "form",
      +          "primary_document",
      +          "document_url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "filter_form_type": {
      +      "description": "Form type filter applied ('all' if none specified)",
      +      "type": "string"
      +    },
      +    "fiscal_year_end": {
      +      "description": "Company's fiscal year end date (MMDD format)",
      +      "type": "string"
      +    },
      +    "sic_description": {
      +      "description": "SEC SIC industry classification description",
      +      "type": "string"
      +    },
      +    "state_of_incorporation": {
      +      "description": "State where company is incorporated",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "cik",
      +    "company_name",
      +    "sic_description",
      +    "state_of_incorporation",
      +    "fiscal_year_end",
      +    "filter_form_type",
      +    "filings"
      +  ],
      +  "type": "object"
      +}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "cik": "320193"
      +  },
      +  {
      +    "cik": "1018724",
      +    "form_type": "10-K"
      +  }
      +]
  5. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds one genuinely useful behavioral note — that the response's matched_by field reveals whether a ticker or name was resolved — but says nothing about how many filings "recent" covers, ordering, pagination, or rate limits against the SEC.

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 sentences, front-loaded with the core action and scope, with the filter and the matched_by caveat following in priority order. The enumeration of returned fields is partly redundant given an output schema exists, which keeps it just short of ideal.

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?

With rich annotations, an output schema, and full parameter documentation, the description only needs to frame the call, which it does. The remaining gap is the undefined scope of "recent" (how many filings, ordering, truncation), which an agent may need to know to interpret results.

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 both parameters are already documented with formats and examples. The description restates the CIK/ticker/name acceptance and the optional form-type filter without adding syntax or edge-case meaning beyond the schema, which is the baseline case for a fully documented 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?

The description names a specific verb and resource ("Get recent SEC filings for a company") plus the three accepted identifiers and the fields returned (dates, form types, accession numbers). That is enough to separate it from a facts-oriented sibling, though it never names an alternative explicitly, so the differentiation is inferred rather than stated.

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 phrasing: look up a company's filings, and optionally narrow by form type. There is no statement of when to prefer this over a company-facts or register-search sibling, and no prerequisites or exclusions are given.

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.