Skip to main content
Glama

MetricDuck — Financial Analysis

by com.metricduck
OverviewDiscussionsAdmin

List Filing Sections

list_filings
Read-only

Use this when the user asks which filings a company has made — its 10-K annual reports, 10-Q quarterly reports, 8-K current reports (earnings releases, events, call transcripts), proxy statements (DEF 14A), or 20-F / 40-F / 6-K for foreign issuers — or needs one specific past filing. Returns each filing's form type, dates and accession number, plus per-section sizes (words, chunks, tables) for 10-K / 10-Q / DEF 14A; 8-Ks return filing metadata only. Default: last 2 years; data from 2013.

Use it to:

  • get the accession_number of a specific past filing (for get_filing_section or get_xbrl_facts)

  • pin one periodic filing (10-K / 10-Q, e.g. FY2020 Q3) with fiscal_year + fiscal_period — 8-K sub-types are not period-indexed, so pair form_subtype with years instead

  • see the section inventory with sizes, or confirm a filing exists For what matters in the latest filing use get_filing_index; for earnings-call trends, compare_earnings_calls.

Delisted / acquired companies: pass cik (10-digit, zero-padded) instead of ticker and set include_delisted=true. SEC's ticker registry excludes delisted issuers, so ticker-only calls 404 even when MetricDuck holds the filings. Example: Spirit Airlines (cik="0001498710").

Responses capped at ~20K chars; narrow via form_type, fiscal_year, or fewer years.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cikNo10-digit SEC CIK as alternative to ticker. Use for delisted/acquired companies (e.g., Z=Zillow ticker may not resolve; pass cik='0001617640' instead). Either ticker or cik required.
yearsNoYears of filing history (default 2, max 7). Ignored when fiscal_year is set.
tickerNoCompany ticker symbol (e.g., 'AAPL'). Must be exact. Either ticker or cik required.
form_typeNoFilter by form type: 10-K annual, 10-Q quarterly, 8-K current reports, DEF 14A proxy; 20-F/40-F annual and 6-K interim for foreign private issuers. Other forms (424B2, FWP, 13F-HR, 4): search_sec_filings(query, company, form_type, sections=false) links the filing on EDGAR (company: the 10-digit CIK; date_from for older filings).
fiscal_yearNoPick a specific fiscal year (e.g., 2020). Resolved via the XBRL period index — correct for non-calendar fiscal years (a 10-K filed Feb 2024 is FY2023). Alone, lists all of that fiscal year's filings (10-K + its 10-Qs); combine with fiscal_period to pin one. Overrides years. DEF 14A / non-XBRL forms are not period-indexed. Data horizon: 2013+.
form_subtypeNoFilter 8-K filings by sub-type (derived from section inventory): earnings releases; event = M&A / exec changes / debt; transcript = earnings calls; other = misc. Implicitly narrows to form_type='8-K'. CANNOT be combined with fiscal_year/fiscal_period — 8-Ks carry no XBRL fiscal-period focus to pin against; use `years` and read the implied period off each row.
vantage_dateNoAs-of vantage (YYYY-MM-DD): only list filings filed ON OR BEFORE this date (point-in-time). Omit to list the most recent filings. For vantages older than the `years` window, pass a larger `years`.
fiscal_periodNoPick a specific fiscal period. FY = annual (10-K / 20-F / 40-F); Q1/Q2/Q3 = quarterly (10-Q). The 4th quarter is reported in the annual 10-K, so Q4 is treated as FY. Combine with fiscal_year to pin a single filing.
include_delistedNoOpt in to historical data for a delisted company. Default false returns a structured 'delisted' error (HTTP 410) naming the delisting date. Querying by cik bypasses this gate. Applies to 10-K/10-Q/DEF 14A only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / cik / pattern
      Previous value: -"^\\d{10}$"New value: +"^\\d{1,10}$"
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, non-destructive, open-world), and the description adds real behavioral context beyond them: default 2-year window, 2013 data horizon, ~20K char response cap with narrowing advice, 8-Ks returning metadata only, and the delisted-company 410 gate that cik bypasses.

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-loads the trigger and is organized into scannable bullets, but it is long and repeats content already present in the schema parameter descriptions (delisted/cik guidance, fiscal-period indexing). A trim would help, though nothing is wasted enough to hurt usability.

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?

With no output schema, the description correctly carries the return-shape burden: form type, dates, accession number, and per-section sizes for 10-K/10-Q/DEF 14A versus metadata-only 8-Ks. Combined with the data horizon, defaults, and cap, an agent has everything needed to call and interpret results.

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% and schema descriptions are already detailed, but the description adds cross-parameter interaction semantics: fiscal_year overriding years, Q4 collapsing into FY, form_subtype being incompatible with fiscal_year/fiscal_period, and cik bypassing include_delisted. Some of this repeats the schema, so it lands just above the baseline rather than at 5.

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 (list a company's filings) and immediately enumerates the covered form types with plain-English glosses. It also explicitly distinguishes itself from siblings get_filing_index and compare_earnings_calls, so an agent can route without opening schemas.

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?

Opens with an explicit 'Use this when...' trigger and follows with three concrete uses (fetch accession_number, pin a periodic filing, inventory sections/confirm existence), plus named alternatives for adjacent needs. The 8-K vs fiscal-period indexing rule is spelled out as a when/when-not condition.

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

All MetricDuck — Financial Analysis toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources