Skip to main content
Glama

Kaleidoscope MCP (SEC & financial data)

Quarterly Financials

get_fundamentals
Read-onlyIdempotent

Get financial fundamentals for a company from SEC XBRL data — quarterly values with year-over-year growth rates, margins, margin deltas, and PIT-integrity metadata. Includes COGS, inventory, capex, operating lease assets/liabilities, interest expense, dividends paid, research_development, total_current_assets and total_current_liabilities (for working capital / current ratio), total_assets and total_liabilities alongside the original revenue/margin/EPS/cash-flow set. period='annual' returns fiscal-year rows (10-K/20-F/40-F) instead of quarters; annual rows carry the values and PIT metadata but no YoY, margin or flag fields. Use this when asked about actual financial performance, profitability, balance sheet, cash flow, capex intensity, lease obligations, or interest burden.

ROIC + beta (2026-11-09): every row carries roic = operating_income x (1 - tax rate) / (total_debt + stockholders_equity), a ratio (0.25 = 25%). On quarterly rows it is ONE quarter, not annualized (AAPL ~16%); for 'what is the ROIC' use period='annual' (AAPL FY2026 69%). Null for filers that don't tag operating income (JNJ, CVX, XOM, most banks and insurers); runs high for captive-finance filers whose finance-arm debt isn't in total_debt (Ford). The top-level beta block is the stock's beta vs SPY over 2 years of daily total returns (with r_squared, n_obs, as_of); null under 250 observations; low r_squared is real, not an error.

Point-in-time integrity (2026-06-10): each row carries is_restated (bool — True iff any of revenue/net_income/operating_income/eps/operating_cash_flow for this period was later filed with a >2% difference) and first_reported_date (the date the value first became knowable, = filed_at of accession_number). Fundamentals already store as-first-reported by default (XBRL's extractor picks the earliest-filed accession), so for backtests that want the strictly-PIT subset, filter is_restated=False. IBM 2019-Q4 is the canonical restated case (re-presented in the post-Kyndryl-spinoff 10-K comparatives).

YoY + margin deltas (2026-06-10): rows now carry operating_income_yoy, gross_profit_yoy, fcf_yoy, capex_yoy, shares_outstanding_yoy (the numeric buyback/dilution rate that complements the existing diluting boolean), and gross_margin_delta / operating_margin_delta / net_margin_delta (margin-space deltas, NOT percent-change of margin — so a 0.0125 means the margin expanded by 1.25 percentage points, not 1.25%).

Sector-specific columns surface only when non-null (so a tech filing won't carry pension fields, an oil filing will carry exploration_costs): deferred_revenue / capitalized_contract_cost / contract_cost_amortization (SaaS-style), exploration_costs / mineral_properties (oil/mining), government_assistance (semis / subsidized industries), and pension fields: pension_liability (quarterly — net unfunded amount), pension_plan_assets and pension_obligation (annual / 10-K only — gross plan asset FV and gross PBO/ABO). Coverage of pension fields is ~5-7% of filers (only companies with defined-benefit plans).

Foreign-filer 20-F + IFRS coverage (2026-06-13 → 2026-06-17): the XBRL alias covers 20-F (foreign private issuers — ICLR / ASML / BABA / HAFN / BN / BNTX / TSM / Nubank / argenx / etc.) and 40-F (Canadian MJDS — BCE / Rogers / Teck / Kinross / Pan American Silver / Fairfax / Methanex / Eldorado / etc.). Each row carries TWO honest-labeling keys: reporting_currency (3-letter ISO — USD for domestic filers, CNY/EUR/HKD/JPY/CAD/etc. for foreign filers) and accounting_standard (us-gaap or ifrs-full).

Two read-it-first rules for foreign filers: (1) Monetary values are in NATIVE currency, NOT USD-converted — BABA revenue comes back in CNY, ASML in EUR, BCE in CAD. Always read reporting_currency before quoting a dollar figure (no risk of misreading €32B as $32B). Caller does any FX conversion. (2) NEVER compare margins or growth rates across accounting_standard — IFRS and us-GAAP differ on lease classification, asset revaluation, financial-instruments measurement, business combinations, etc. A 32% gross margin under IFRS is NOT comparable to 32% under us-GAAP without analyst-side normalization.

IFRS bank coverage uses revenue_bank_computed fallback (net interest + fee income — HSBC / BBVA / Lloyds / Barclays / ING / Santander / Westpac / Sumitomo / etc.). Bank revenue ~75-100% of true depending on filer — trading + insurance income missing. HSBC has the biggest gap (~25% under-stated). Banks that tag Revenue directly (WBC, NWG, Lloyds) match published numbers exactly. IFRS REITs use RentalIncomeFromInvestmentProperty fallback (Gazit-Globe etc.). Filers still missing: mixed-currency tag filings (AZN, NVO — file NetIncome in USD but Revenues in GBP/DKK) and 6-K interim results (futures v2 funnel).

Coverage: ~4,400 public companies + foreign-filer 20-F additions, quarterly data back to ~2009. Class-share aliases (GOOGL/GOOG, BRK-A/BRK-B, etc.), preferreds, and other ticker variants are auto-resolved via Atlas before the XBRL lookup — when aliasing is in play, the response includes a resolved_via_atlas block showing the queried ticker, the XBRL canonical ticker, and the CIK.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_fundamentals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of periods to return, most recent first (default: 8, max: 20)
periodNoquarterly (default) or annual (one row per fiscal year)quarterly
tickerNoCompany: exchange ticker (AAPL), CIK (1803498), a non-traded fund's symbol (BCRED, HLEND, OCIC) or company name ('Blackstone Real Estate Income Trust'). `company` is an alias of this.
companyNoSame as `ticker`: ticker, CIK, fund symbol or name.
end_dateNoLatest fiscal period end date (YYYY-MM-DD, optional)
start_dateNoEarliest fiscal period end date (YYYY-MM-DD, optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / company
      Added value: +{
      +  "description": "Same as `ticker`: ticker, CIK, fund symbol or name.",
      +  "type": "string"
      +}
    • changedInput schema / properties / ticker / description
      Previous value: -"Stock ticker symbol (e.g. AAPL, NVDA, MRNA)"New value: +"Company: exchange ticker (AAPL), CIK (1803498), a non-traded fund's symbol (BCRED, HLEND, OCIC) or company name ('Blackstone Real Estate Income Trust'). `company` is an alias of this."
    • removedInput schema / required
      Removed value: -[
      -  "ticker"
      -]
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already mark this as read-only, idempotent, non-destructive, and closed-world, and the description adds substantial behavioral context beyond them. It discloses foreign-currency reporting, IFRS vs us-GAAP comparability limits, restatement/PIT caveats, ROIC quirks, bank revenue fallback behavior, sector-specific column availability, and ticker aliasing behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded and organized with bold section headers, but it is extremely long and dense with edge-case examples, dates, and company-specific notes. Much of the content is useful, yet it could be tightened without losing critical guidance.

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?

For a complex financial-data tool with six optional parameters and no output schema, the description is highly complete. It covers coverage, currencies, accounting standards, restatements, sector columns, ROIC/beta behavior, aliasing, and known limitations well enough for an agent to use the tool 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, but the description adds meaningful semantics beyond the schema. It explains the behavioral difference for period='annual' versus quarterly rows and documents ticker resolution via Atlas, including the resolved_via_atlas response block.

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 states a specific verb and resource: get financial fundamentals for a company from SEC XBRL data, including quarterly values, YoY growth, margins, and PIT metadata. It is clear what the tool returns, but it does not explicitly distinguish itself from related siblings such as sec_power_fundamentals, mars_reit_fundamentals, or screen_fundamentals.

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 clear when-to-use guidance: actual financial performance, profitability, balance sheet, cash flow, capex intensity, lease obligations, and interest burden. It also explains quarterly vs annual behavior, but it does not explicitly state when to use a sibling tool instead.

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