Skip to main content
Glama

finance.company-facts

Retrieve key financial metrics for any US public company by stock ticker. Returns annual and quarterly values for revenue, earnings, cash flow, and balance sheet items from SEC filings.

Instructions

Curated XBRL financial metrics for a US public company by stock ticker. Returns ~15 top-line metrics (revenue, gross profit, operating income, net income, EPS, R&D, total assets, liabilities, equity, cash, debt, operating cash flow, capex, shares outstanding) with their most recent annual + quarterly values. Each metric returns the originating form (10-K/10-Q), period dates, fiscal year/period, and filed date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesUS stock ticker (case-insensitive).
metricsNoOptional comma-separated subset of metric keys. Available: revenue, grossProfit, operatingIncome, netIncome, eps, epsDiluted, rdExpense, totalAssets, totalLiabilities, stockholdersEquity, cash, longTermDebt, operatingCashFlow, capex, sharesOutstanding. Omit to get all ~15.
annualLimitNoMax annual (FY) values per metric, most recent first.
quarterlyLimitNoMax quarterly values per metric, most recent first. 0 to skip quarterly.
Behavior4/5

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

With no annotations, the description fully covers the read-only behavior, returns structure (annual + quarterly values, originating form, period details), and default metric set. It lacks mention of auth or rate limits, but the context is adequate.

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?

The description is a single paragraph that is information-dense and front-loaded with the core purpose. It could be slightly improved with bullet points for readability, but it is not overly verbose.

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?

The description comprehensively explains the tool's output format and parameters without an output schema. It covers the metric list, filtering options, and limit behavior, making it sufficient for an agent to use 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?

All parameters have schema descriptions (100% coverage), and the description adds value by listing the available metric keys, explaining the comma-separated semantics, and clarifying default behaviors for limits and metric selection.

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 explicitly states the tool fetches curated XBRL financial metrics for a US public company by stock ticker, lists ~15 specific top-line metrics, and distinguishes it from sibling tools like finance.company-profile or finance.sec-filings.

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?

The description clearly indicates the tool is for obtaining key financial metrics for a US public company, but does not explicitly state when to avoid using it or suggest alternative tools in the finance family.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/2s-io/sdk'

If you have feedback or need assistance with the MCP directory API, please join our Discord server