Skip to main content
Glama

Recent SEC filings of a company

get_filings
Read-only

Returns a company's recent SEC filings, classified (earnings, 8-K items, notes and loans, share offerings, prospectuses…), each with its acceptance time, accession number and sec.gov link; a financing filing carries what it says: amount, coupon, maturity, status, the sentence it comes from. Insider filings (Forms 3, 4, 5 and 144) are left out unless asked for: their purchases and sales are summed over 90 days in insiderFlow90d, with the filer's role, not the person's name. Filings are dated by acceptance time, not filing date. Use it when the user asks what a company has filed, announced, borrowed or raised recently.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_filings"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoFilings to return (default 15, max 50).
symbolYesTicker or company name, e.g. NVDA, AMD, ASML, 'nvidia', 'taiwan semiconductor'. Case-insensitive.
insidersNoInclude insider filings (Forms 3, 4, 5 and 144), left out by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +50
    • addedInput schema / properties / limit / minimum
      Added value: +1
  2. Changed1 schema field changed
    • addedInput schema / properties / insiders
      Added value: +{
      +  "description": "Include insider filings (Forms 3, 4, 5 and 144), left out by default.",
      +  "type": "boolean"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover the read-only safety profile, and the description goes well beyond them: it discloses the classification scheme, the insider exclusion default, the fact that insider data is aggregated into `insiderFlow90d` over 90 days by filer role rather than name, and the non-obvious dating rule (acceptance time, not filing date). Those are exactly the behaviors an agent could otherwise get wrong.

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 the core return description and terminated by the usage trigger, with no filler sentences. The middle clauses are dense and semicolon-chained, which costs a little readability, but every clause carries substantive information.

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?

There is no output schema, so the description must describe return values, and it does: per-filing fields, the financing-filing payload, and the `insiderFlow90d` aggregate. Combined with the dated-by-acceptance-time rule and the default exclusion, an agent has everything needed to call it and interpret the result.

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%, so the baseline is 3, but the description adds real meaning the schema lacks: it explains what `insiders` actually changes about the output (the 90-day summed `insiderFlow90d` keyed by role) and why dating is based on acceptance time. It does not add anything for `limit` beyond what the schema already says.

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 ('Returns a company's recent SEC filings') and then enumerates the classification taxonomy, per-filing fields (acceptance time, accession number, sec.gov link) and financing detail. It also carves out insider forms (3, 4, 5, 144), which separates it from the sibling get_insider_trading without the agent needing to open either schema.

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 final sentence gives an explicit trigger: 'Use it when the user asks what a company has filed, announced, borrowed or raised recently.' It also states the default exclusion of insider filings and the condition that overrides it ('unless asked for'). What's missing is naming the actual sibling to use for insider-only questions, leaving that inference to the reader.

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.