Skip to main content
Glama

mkts Market Data

Get company fundamentals

get_fundamentals
Read-onlyIdempotent

Get annual or quarterly financial-statement time series for a stock: income statement, balance sheet and cash flow, built from the company's own SEC filings (source "sec-edgar"), or from the equities provider for funds and companies EDGAR does not cover. Values are in the reporting currency the response names, which is not always USD. Modules can return all statements or a smaller financials, balance-sheet, or cash-flow payload.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
moduleNofinancials is the income statement (revenue, margins, EPS); choose one module for a smaller response, or all for every statement.all
periodNoFiscal years or fiscal quarters.annual
symbolYesUS stock or ETF ticker, e.g. MSFT.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / module / description
      Added value: +"financials is the income statement (revenue, margins, EPS); choose one module for a smaller response, or all for every statement."
    • addedInput schema / properties / period / description
      Added value: +"Fiscal years or fiscal quarters."
    • addedInput schema / properties / symbol / description
      Added value: +"US stock or ETF ticker, e.g. MSFT."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world behavior, so the bar is lower, and the description adds genuine context beyond them: the upstream source varies by symbol type, and reported values may be in a non-USD reporting currency. It doesn't mention response size limits, latency, or history depth, but the added source/currency semantics are exactly the non-obvious traits an agent needs.

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 core purpose is front-loaded in the first clause, and each subsequent sentence adds distinct information (source, currency, payload size). It is dense and slightly run-on in the source clause, but no sentence is filler.

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?

For a 3-parameter read tool with no output schema, the description covers what the data represents, where it comes from, currency caveats, and payload granularity. Gaps are minor: no statement of history depth, pagination, or what happens when neither source covers a symbol.

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 baseline is 3; the description earns an extra point by explaining the payload-size tradeoff between 'all' and a single module, and by tying period to 'fiscal years or fiscal quarters' data rather than calendar periods. Enum member meanings are largely already in the schema, so it only modestly exceeds it.

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?

Opens with a specific verb+resource+scope: annual/quarterly financial-statement time series for a stock, naming the three statements covered. This cleanly separates it from siblings like get_filings (raw filings) and get_asset_series (prices), so an agent can pick it 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains the data-source resolution rule (SEC EDGAR filings first, provider fallback for funds and non-EDGAR companies) and when to pick a smaller module payload, which is real usage guidance. It stops short of naming alternatives or stating exclusions (e.g. 'for raw filings use get_filings'), so it's clear context without explicit routing.

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