Sec Xbrl

Get Company Financials

get_company_financials

Read-onlyIdempotent

High-level summary of a public US company's annual (10-K) financials: revenue, net income, total assets, cash, EPS, etc. Returns clean numerical values with the XBRL tag used and the period-end date. By default returns the most recent fiscal year; pass fiscal_year_end to get a specific year (e.g. "2024-12-31" for Tesla FY2024 or just "2024" to auto-match the year). Prefer this over get_company_facts/get_company_concept for any single-company financial snapshot question. Pass a CIK (e.g. "320193") or a ticker (e.g. "AAPL"; auto-resolves to CIK).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`company`	Yes	CIK (e.g., "320193", "0000320193") OR ticker symbol (e.g., "AAPL", "TSLA", "MSFT"). Ticker is auto-resolved to CIK via SEC EDGAR.
`fiscal_year_end`	No	Optional. Pass a 4-digit fiscal year ("2024") to get values from any 10-K period ending in that calendar year, OR a specific period-end date ("2024-12-31"). Omit to get the most recent fiscal year.

Output Schema

TableJSON Schema

Name	Required	Description
`cik`	Yes	SEC Central Index Key
`revenue`	Yes	Total revenue from annual filing
`eps_basic`	Yes	Earnings per share (basic) from annual filing
`net_income`	Yes	Net income from annual filing
`period_end`	Yes	Period-end date from most recent 10-K (ISO format)
`entity_name`	Yes	Company legal entity name
`eps_diluted`	Yes	Earnings per share (diluted) from annual filing
`fiscal_year`	Yes	Fiscal year of filing
`rnd_expense`	Yes	Research and development expense from annual filing
`gross_profit`	Yes	Gross profit from annual filing
`total_assets`	Yes	Total assets from annual filing
`operating_income`	Yes	Operating income from annual filing
`total_liabilities`	Yes	Total liabilities from annual filing
`stockholders_equity`	Yes	Stockholders equity from annual filing
`cash_and_equivalents`	Yes	Cash and cash equivalents from annual filing
`common_shares_outstanding`	Yes	Common stock shares outstanding from annual filing

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 26, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructiveHint. The description adds context about return format (clean numerical values, XBRL tag, period-end date) and auto-resolution of ticker to CIK, providing additional behavioral insight without contradicting annotations.

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?

The description is short (three sentences) and front-loaded with the core purpose. Every sentence adds value: what it returns, how to specify the year, and sibling preference. No fluff.

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?

Given the tool's simplicity (2 params, output schema exists), the description covers inputs, output nature, and sibling alternatives. It implicitly restricts to US public companies but could explicitly state that limitation. Output schema likely explains return values, so no missing critical info.

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 baseline 3. The description adds meaning by explaining the 'company' parameter accepts CIK or ticker with auto-resolution, and the 'fiscal_year_end' parameter accepts 4-digit year or specific date, with default behavior detailed. This goes beyond the schema's basic description.

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 clearly states it provides a high-level summary of a public US company's annual (10-K) financials with specific metrics. It explicitly distinguishes itself from siblings get_company_facts and get_company_concept by stating preference for single-company snapshot questions.

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?

The description gives explicit guidance: 'Prefer this over get_company_facts/get_company_concept for any single-company financial snapshot question.' It also explains how to specify the fiscal year and default behavior, effectively telling the agent when to use this tool.

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

All Sec Xbrl tools Inspect

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.