Skip to main content
Glama
datavidence

datavidence-financials

Official
by datavidence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List SEC filings

list_filings
Read-onlyIdempotent

Check a company's recent SEC filings on EDGAR by ticker or CIK, filter by form like 10-K, and identify available fiscal years before fetching financial statements.

Instructions

List a company's recent SEC filings (newest first) from the EDGAR submissions index — a lean company header plus filing rows.

Identify the company by ticker OR cik. Optionally filter by form (e.g. "10-K", prefix-matched so it includes amendments like "10-K/A") and cap the number of rows with limit (1-100). Use this to discover which fiscal years or filings are available before calling get_financials.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cikNoSEC Central Index Key, e.g. "0000320193". Give this or `ticker`.
formNoForm type filter, prefix-matched, e.g. "10-K" (includes 10-K/A).
limitNoMaximum rows to return (1-100).
tickerNoStock ticker, e.g. "AAPL". Give this or `cik`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / cik / description
      Added value: +"SEC Central Index Key, e.g. \"0000320193\". Give this or `ticker`."
    • addedInput schema / properties / form / description
      Added value: +"Form type filter, prefix-matched, e.g. \"10-K\" (includes 10-K/A)."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows to return (1-100)."
    • addedInput schema / properties / ticker / description
      Added value: +"Stock ticker, e.g. \"AAPL\". Give this or `cik`."
  2. First observedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds valuable behavioral context: newest-first ordering, prefix-matching for form types (e.g., includes 10-K/A), and output shape (a lean company header plus filing rows).

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?

Two sentences, action-first, and includes all key details (identification, filters, limit, order, use case) without filler. Every sentence earns its place.

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 4-parameter filtered list tool with no output schema, the description explains input, filtering, ordering, and intended use before get_financials. It stops short of listing specific filing row fields, but the mention of discovering fiscal years/filings gives sufficient context for an agent to use 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 baseline is 3. The description repeats the ticker-or-cik relationship and prefix-matching behavior already present in the schema, adding minimal new semantics beyond the schema.

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 ('List'), resource (SEC filings from the EDGAR submissions index), and order (newest first). It also names the sibling get_financials as the follow-up, clearly distinguishing this tool's role as a discovery step.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this to discover which fiscal years or filings are available before calling get_financials,' providing a concrete use case and naming the alternative for actual financial data. The ticker-or-CIK identification and filter options further clarify when to use it.

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

Deploy Server

Other Tools