Skip to main content
Glama

Company-reported metrics (adjusted and operating)

company_kpis
Read-onlyIdempotent

Return the metrics a company reports in its own earnings releases and reports: adjusted (non-GAAP) measures such as adjusted EBITDA or adjusted EPS, and operating KPIs such as segment or product sales. Each value carries the filer's row label, confidence (high: printed identically in two or more places; medium: printed once) and a proof id; proof_get on it returns the exact citation: accession, document, table, row and value index, character span, the raw printed text and the GAAP reconciliation table. Adjusted metrics are the company's own definitions: say "as reported by the company (non-GAAP)", never call them GAAP and never compare them across companies. Values two documents print differently are withheld and not returned (data.withheld counts them). data.metrics lists the company's metrics; filter with metric, kind, period_type, from and to. Percent metrics are percent points. Use it when the question is about a non-GAAP figure or an operating metric the standardized statements do not carry.

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": {
      "kind": "adjusted",
      "limit": 10,
      "company": "ticker:MSFT"
    },
    "name": "company_kpis"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast period end, inclusive (YYYY-MM-DD).
fromNoFirst period end, inclusive (YYYY-MM-DD).
kindNoadjusted: non-GAAP measures; operating: operating statistics.
as_ofNoKnowledge date or timestamp (YYYY-MM-DD or RFC 3339). The answer is what FinancialMD knew at that instant: only facts whose known interval contains as_of. Omit for the current view.
limitNoMaximum number of periods or items to return (default 50, at most 1000).
cursorNoOpaque cursor from a previous page (data.next_cursor).
metricNoOnly this metric slug (for example adjusted_ebitda); data.metrics lists them.
companyYesCompany identifier: a FinancialMD id ("fmd_01H..."), an SEC CIK ("cik:320193"), or a ticker ("ticker:AAPL", optionally with the MIC "ticker:AAPL.XNAS"). A bare ticker like "AAPL" is accepted and sent as ticker:AAPL. An issuer on an EU or UK regulated market that does not file with the SEC has no CIK: pass its LEI ("lei:IOG4E947OATN0KJYSD45") or its fmd_ id.
period_typeNoOnly this period type.

Output Schema

NameRequiredDescriptionDefault
dataNo{ items: [{ metric, reported_label, label, period_type, period_start, period_end, value, confidence, confidence_label, corroborated_by, reconciliation_anchor }], next_cursor, metrics, withheld, note }
metaNoRequest metadata: request_id, as_of, company resolution, coverage, pipeline_version, licence, terms, proof_base.
errorNoPresent only on isError results: the API error code and message plus remedy hints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / company / description
      Previous value: -"Company identifier: a FinancialMD id (\"fmd_01H...\"), an SEC CIK (\"cik:320193\"), or a ticker (\"ticker:AAPL\", optionally with the MIC \"ticker:AAPL.XNAS\"). A bare ticker like \"AAPL\" is accepted and sent as ticker:AAPL."New value: +"Company identifier: a FinancialMD id (\"fmd_01H...\"), an SEC CIK (\"cik:320193\"), or a ticker (\"ticker:AAPL\", optionally with the MIC \"ticker:AAPL.XNAS\"). A bare ticker like \"AAPL\" is accepted and sent as ticker:AAPL. An issuer on an EU or UK regulated market that does not file with the SEC has no CIK: pass its LEI (\"lei:IOG4E947OATN0KJYSD45\") or its fmd_ id."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, and the description goes well beyond them: it discloses the confidence taxonomy (high = printed in two or more places, medium = printed once), the proof_id/citation chain via proof_get, and the withholding rule for conflicting values with data.withheld as the counter. The only gap is that it does not say how results are ordered or how large a page default actually yields in practice, though limit/cursor are in the schema.

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?

It is front-loaded with purpose, then evidence/provenance, then the compliance caveat, then filter mechanics, then the use-case trigger — a sensible order with no filler. It runs long and some sentences chain several clauses (confidence taxonomy and proof fields in one breath), which costs a little scannability.

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 nine parameters, an output schema and a provenance chain to proof_get, the description supplies everything an agent needs: what is and is not returned, how to page and filter, how to resolve a citation, and the non-GAAP reporting constraint. Return-value shapes are left to the output schema, which is the right division of labor.

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 schema already carries per-parameter meaning and this is baseline-plus. The description still adds useful orientation: it lists which parameters act as filters and points to data.metrics as the source of valid metric slugs, plus the domain caveat that percent metrics are percent points rather than fractions.

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 verb and resource ('Return the metrics a company reports in its own earnings releases') and enumerates the two content classes (adjusted non-GAAP measures, operating KPIs) with examples. It also separates itself from the standardized statements siblings by scoping to company-defined figures, so an agent can pick it without opening any schema.

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 final sentence gives an explicit trigger ('when the question is about a non-GAAP figure or an operating metric the standardized statements do not carry'), which routes the agent away from financials_standardized. It also states the filtering entry point (data.metrics, then filter by metric/kind/period_type/from/to), so both selection and invocation are covered.

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