Skip to main content
Glama
datavidence

datavidence-financials

Official
by datavidence
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get financial statements for many companies

get_financials_batch
Read-onlyIdempotent

Retrieve normalized US-GAAP financials for up to 25 companies in one call—compare peers or scan a set for a single fiscal year. Each symbol returns data or an error hint, counting as one request.

Instructions

Retrieve normalized US-GAAP financials for MANY companies in one call — use this to compare peers or scan a set for a single fiscal year.

Pass companies as comma-separated tickers (e.g. "AAPL,MSFT,GOOGL") and/or ciks; up to 25 symbols total, all for the same year. as_of, include_provenance, and include_ratios behave as in get_financials and apply to every symbol. Each company returns its own result — either data or an error with a recovery hint — so one bad symbol never fails the batch. The whole call counts as a SINGLE request against your monthly quota, so prefer it over many get_financials calls when you need several companies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ciksNoComma-separated SEC CIKs (25 symbols max, with `tickers`).
yearYesFiscal year, e.g. 2023.
as_ofNoISO date YYYY-MM-DD. Return figures as originally reported on that date (no look-ahead). Omit for the latest reported figures.
tickersNoComma-separated tickers, e.g. "AAPL,MSFT,GOOGL" (25 symbols max, with `ciks`).
include_ratiosNoAdd margins, ROA/ROE and leverage computed from the same statements.
include_provenanceNoAttach the SEC accession, filed date and EDGAR URL behind every value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / as_of / description
      Added value: +"ISO date YYYY-MM-DD. Return figures as originally reported on that date (no look-ahead). Omit for the latest reported figures."
    • addedInput schema / properties / ciks / description
      Added value: +"Comma-separated SEC CIKs (25 symbols max, with `tickers`)."
    • addedInput schema / properties / include_provenance / description
      Added value: +"Attach the SEC accession, filed date and EDGAR URL behind every value."
    • addedInput schema / properties / include_ratios / description
      Added value: +"Add margins, ROA/ROE and leverage computed from the same statements."
    • addedInput schema / properties / tickers / description
      Added value: +"Comma-separated tickers, e.g. \"AAPL,MSFT,GOOGL\" (25 symbols max, with `ciks`)."
    • addedInput schema / properties / year / description
      Added value: +"Fiscal year, e.g. 2023."
  2. First observedv0.1.2

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already show read-only, open-world, and idempotent behaviortin less detail. The description adds significant behavioral context: per-company data-or-error responses with recovery hints, batch failure isolation, no-look-ahead as_of semantics, and single-request quota accounting. This exceeds what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and well-structured: it leads with the primary purpose, then covers input constraints, parameter behavior, error handling, and quota implications in a logical order. Every sentence contributes actionable information without redundancy.

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?

For a batch tool with no output schema, the description covers the key operational aspects: input format, limits, shared year constraint, per-symbol error handling, and quota implications. It also routes to get_financials for single-company needs. Nothing critical is missing for correct invocation.

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 all parameters are documented in the schema. The description adds value by explaining aggregate semantics not visible in the schema: the combined 25-symbol limit across tickers and ciks, all symbols sharing one year, and that shared parameters behave identically to get_financials.

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 states a specific verb and resource: 'Retrieve normalized US-GAAP financials for MANY companies in one call.' It clearly distinguishes itself from the sibling get_financials by emphasizing batch retrieval and peer comparison/scans.

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?

Explicitly tells when to use the tool: 'compare peers or scan a set for a single fiscal year,' and directly names the alternative get_financials while giving a concrete condition ('prefer it over many get_financials calls when you need several companies').

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

Deploy Server

Other Tools