Skip to main content
Glama

Company Financials API - revenue, profit, EPS, cash flow from SEC filings

company_financials
Read-onlyIdempotent

Normalized financial statements of US-listed companies straight from SEC XBRL filings (10-K/10-Q): revenue, gross profit, operating and net income, EPS, assets, liabilities, equity, cash, operating cash flow, capex, free cash flow, net margin, long-term debt. Annual or quarterly, up to 20 years, by ticker or CIK. One clean row per period instead of thousands of raw XBRL facts. Free: 25 calls/day per IP. Paid: $0.005 per call via x402 at https://radarbg.com/x402/company-financials.

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": {
      "years": 5,
      "period": "annual",
      "ticker": "AAPL"
    },
    "name": "company_financials"
  }
}

Input Schema

NameRequiredDescriptionDefault
cikNoOr SEC CIK number
yearsNoHow many years back
periodNoannual or quarterlyannual
tickerNoUS ticker, e.g. AAPL (or company name)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent and open-world behavior, and the description adds materially beyond that: the data source (SEC XBRL), the 20-year depth, the free tier of 25 calls/day per IP and the paid $0.005/call x402 endpoint. Cost and rate-limit disclosure is exactly the extra context annotations cannot carry. It stops short of describing error or missing-data behavior, so it is not a full 5.

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?

A single dense paragraph with no filler: what it is, what fields it returns, what granularity, and what it costs. The long metric enumeration is somewhat list-like, but every item earns its place by telling the agent which fields are available. Front-loading the core purpose keeps it scannable.

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 return-value burden and does so by enumerating the metrics and stating the row-per-period shape. Combined with the query dimensions (ticker/CIK, period, years) and pricing model, an agent has everything needed to call it correctly and anticipate the cost.

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 the baseline is 3. The description does reinforce meaning — 'by ticker or CIK' explains the two lookup modes and 'Annual or quarterly, up to 20 years' corroborates the period enum and the years maximum — but it adds no syntax, format or default detail beyond what the schema already states.

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 names a specific resource (normalized financial statements of US-listed companies from SEC XBRL 10-K/10-Q filings) and enumerates the exact metrics returned, from revenue through long-term debt. It also states the scope (annual or quarterly, up to 20 years, by ticker or CIK), so an agent knows precisely what it retrieves without opening the schema.

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 strongly implied — fetch standardized financials for a US-listed company — and the note 'One clean row per period instead of thousands of raw XBRL facts' positions it as the convenient alternative to raw filing data. However, there is no explicit statement of when to use or avoid it, and no named alternative; the guidance must be inferred from the description.

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