Skip to main content
Glama

SEC financial statements (XBRL)

sec_financials
Read-onlyIdempotent

Answers "What were Apple's revenue and net income over the last five years?", "Is Tesla's free cash flow positive?" or "How fast is Nvidia growing quarter over quarter?". Returns a US public company's key financial-statement figures for its latest fiscal years (annual, from 10-Ks) or single quarters (quarterly), newest first, from the XBRL data companies file with the SEC: income statement (revenue, cost of revenue, gross profit, R&D, SG&A, operating income, pretax income, tax, net income, basic and diluted EPS, diluted shares), balance sheet (cash, current and total assets and liabilities, long-term debt, equity) and cash flow (operating cash flow, capex, free cash flow, dividends, buybacks), plus gross, operating and net margins and year-over-year revenue growth. Fourth quarters and single-quarter cash flows, which companies only report as full-year or year-to-date totals, are derived and flagged in derived. Each period cites the latest filing that reports it, so restated figures replace original ones. Up to 20 periods per call, back to about 2009; fiscal_year reaches earlier years. By ticker, CIK or company name. US-GAAP filers only (not IFRS 20-F filers); values in USD. You are only charged when a result is returned: invalid input (400) and upstream failures (4xx/5xx) are not settled. Costs $0.005 USDC per call via x402. Paid per call with x402 inside MCP (see the server instructions).

Input Schema

NameRequiredDescriptionDefault
cikNoSEC Central Index Key, e.g. 320193. Use this, `ticker` or `company`.
viaNoOptional: the tool whose next_calls suggested this call (filled in for you).
limitNoHow many periods to return, newest first (1-20, default 5).
periodNoFiscal years from 10-Ks (annual, the default) or single quarters (quarterly).annual
tickerNoUS stock ticker, e.g. AAPL, MSFT, BRK-B. Use this, `cik` or `company`.
companyNoCompany name, e.g. "Apple" or "Coca-Cola". Use this, `ticker` or `cik`; a name matching several companies returns their tickers, free.
fiscal_yearNoReturn periods up to this fiscal year (the calendar year the fiscal year ends in) instead of the latest, e.g. 2019.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / via
      Added value: +{
      +  "description": "Optional: the tool whose next_calls suggested this call (filled in for you).",
      +  "maxLength": 64,
      +  "type": "string"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (which already declare readOnly/idempotent/non-destructive), the description discloses derived fourth quarters and cash flows with a `derived` flag, restatement behavior ('latest filing that reports it, so restated figures replace original ones'), period limits, filing coverage back to 2009, currency/filer scope, and the billing model (charged only on returned results; 400/4xx not settled). That is unusually rich behavioral context.

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?

It is front-loaded with representative questions then a dense but information-rich block, with almost every clause carrying load (fields, derivation rules, limits, pricing). The example questions are somewhat bulky and the single-paragraph wall of text could be better segmented, keeping it from a 5.

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 carries the full burden of describing return values, and it does: enumerated statement line items, derived margins and YoY growth, the `derived` flag, period counts, restatement semantics, and billing. An agent has everything needed to call it correctly.

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 and the schema does the heavy lifting. The description still adds meaning beyond the schema: period selection maps to filing types (annual from 10-Ks vs single quarters), fiscal_year reaches earlier years, and identifiers are accepted by ticker/CIK/company name.

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?

The description states a specific verb+resource: it returns a US public company's key financial-statement figures (income statement, balance sheet, cash flow) from SEC XBRL data. The example questions and enumerated field lists make it immediately distinguishable from siblings like sec_filing_section or sec_fund_holdings.

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?

It gives concrete usage cues ('What were Apple's revenue over the last five years?', 'Is Tesla's FCF positive?') and states constraints like annual/quarterly period selection, 20-period cap, back to ~2009, and 'US-GAAP filers only (not IFRS 20-F filers)'. It does not explicitly name sibling alternatives or when not to use it, so it stops short of a 5.

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.

Resources