Skip to main content
Glama
SEC EDGAR MCP

SEC EDGAR MCP

by reblickulous

get_financials

Fetch structured SEC XBRL financial data for a public company, including revenue, profit, assets, debt, and EPS across recent annual and quarterly periods to build one-pagers and investment summaries.

Instructions

Fetch structured financial data for a public company from SEC XBRL filings. Returns key metrics (revenue, gross profit, operating income, net income, EBITDA components, total assets, liabilities, cash, debt, EPS) for the last 3 annual periods and 4 quarters. Ideal for building company one-pagers and investment summaries.

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": {
      "cik": "<cik>"
    },
    "name": "get_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikYesCompany CIK number from lookup_company
annual_periodsNoNumber of annual (10-K) periods to return (default 3)
quarterly_periodsNoNumber of quarterly (10-Q) periods to return (default 4)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does substantial work: it names the upstream source (SEC XBRL), the exact metric families returned, and the period depth (3 annual, 4 quarterly). Gaps remain around data-quality edge cases — e.g., what happens when a company's XBRL tags are missing or the CIK is invalid — which matters for financial data that is frequently sparse.

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 what is fetched and from where, followed by return content and use case. The long metric parenthetical is justified because there is no output schema, though it could be trimmed slightly without losing signal.

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 simple three-parameter read tool with no annotations and no output schema, the description covers source, return contents, and period granularity well enough that an agent could call it correctly. Missing pieces are minor: no note on missing-data behavior or on overriding the stated default periods.

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 all three parameters are already documented in the schema, including defaults and the CIK provenance hint ('from lookup_company'). The description's mention of 'last 3 annual periods and 4 quarters' merely restates the schema defaults and adds no new parameter meaning.

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 uses a specific verb and resource: 'Fetch structured financial data for a public company from SEC XBRL filings,' and enumerates the metrics returned. It is clearly distinct from fetch_filing/search_filings/lookup_company by virtue of being a structured-metrics extractor, though it never names those siblings explicitly, so differentiation is implicit 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?

'Ideal for building company one-pagers and investment summaries' gives a positive use context, which is more than nothing. However, there is no when-not guidance, no statement of prerequisites (e.g., resolve CIK via lookup_company first), and no routing to fetch_filing for raw filings or search_filings for discovery.

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