Skip to main content
Glama

Sec Get Company Facts

sec_get_company_facts
Read-onlyIdempotent

Get XBRL financial facts for a company by CIK number, ticker, or company name. Returns latest_annual — revenue, net income, operating income, total assets, liabilities, equity, cash, EPS and shares for the most recent fiscal year (10-K), resolved to whichever XBRL concept the filer currently reports under — plus per-concept detail with the fiscal year and period end on every figure. Concepts the filer has retired (e.g. a pre-ASC-606 Revenues tag) are kept for history but flagged stale and sorted last. Response field matched_by says whether the company was matched by ticker or by company name.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
cikYesCompany CIK ("320193"), ticker ("AAPL"), or name ("Apple") — ticker/name are auto-resolved to a CIK

Output Schema

NameRequiredDescriptionDefault
cikYesCompany CIK number
year_noteNoHow `year` is derived
matched_byNoHow the company was matched: ticker, cik or company_name
company_nameYesOfficial company name
latest_annualYesCanonical line items for the most recent fiscal year — revenue, net_income, operating_income, gross_profit, total_assets, total_liabilities, stockholders_equity, cash_and_equivalents, eps_basic, eps_diluted, shares_outstanding, research_and_development — each resolved to whichever concept the filer currently reports under; null when the filer reports no current value
key_financialsYesPer-concept detail. Current concepts first, retired (stale) concepts last — a stale concept is kept because a historical series still needs it, never silently dropped
stale_conceptsYesConcepts the filer has stopped reporting; present in key_financials flagged stale, never used in latest_annual
latest_period_endNoPeriod end of that most recent annual report (YYYY-MM-DD)
available_conceptsYesTotal number of US-GAAP financial concepts available for this company
latest_fiscal_yearNoFiscal year of the filer's most recent annual report across every concept examined

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / matched_by
      Added value: +{
      +  "description": "How the company was matched: ticker, cik or company_name",
      +  "type": "string"
      +}
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/openWorld, so the description correctly spends its words elsewhere: it discloses that concepts are auto-resolved to the filer's current tag, that retired concepts (e.g. pre-ASC-606 Revenues) are retained but flagged stale and sorted last, and that identifier resolution is reported via matched_by. Those are genuine behavioral traits an agent could not derive from the annotations or schema.

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?

Purpose is front-loaded in the first sentence, which is good. The second sentence is a long clause chain that enumerates return fields (revenue, net income, assets, liabilities, equity, cash, EPS, shares) already covered by the output schema, and that enumeration dilutes the genuinely useful stale-concept detail.

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?

With one parameter, full schema coverage, annotations, and an output schema, the definition is essentially complete for correct invocation. The one gap is edge behavior in identifier resolution — what happens if a name is ambiguous or resolves to nothing — which is unaddressed despite matched_by being advertised.

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 coverage is 100% and there is a single parameter whose schema description already explains CIK/ticker/name resolution, so the schema carries the load. The description restates the same three identifier forms without adding syntax, validation, or failure behavior for ambiguous or unmatched names.

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?

States a concrete verb and resource ('Get XBRL financial facts for a company') and names the three acceptable identifiers, so an agent knows exactly what data comes back. It does not, however, differentiate itself from the similarly named sibling 'company_facts', leaving the agent to guess which one to pick when both plausibly apply.

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?

Usage is only implied: the mention of XBRL/10-K annual fundamentals signals 'use for fundamental financials', but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. versus get_company_filings for raw filings). An agent can infer fit from the content but gets no routing rule.

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.