Skip to main content
Glama

TickerFacts

by com.tickerfacts
OverviewDiscussionsAdmin

Fundamentals for several companies

get_fundamentals_batch
Read-onlyIdempotent

Read annual fundamentals for 1 to 20 comma-separated ticker symbols in one request. Defaults to one newest period per issuer; optional metrics projection. Each result keeps requested/canonical identity and source lineage; unknown tickers produce per-entry errors. No historical point-in-time filtering.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodNoquarterly returns the newest 8 fiscal quarters (or as many as fit) unless quarters is given; annual is the default.
metricsNoComma-separated metric or ratio keys, e.g. revenue,operating_margin,free_cash_flow; omitted means all metrics and ratios. A ratio brings its inputs with it. Metrics: revenue, cost_of_revenue, gross_profit, research_and_development, operating_income, depreciation_and_amortization, ebitda (derived), net_income, eps_diluted, total_assets, total_liabilities, long_term_debt, stockholders_equity, cash_and_equivalents, operating_cash_flow, capex, free_cash_flow (derived), share_repurchases, dividends_paid, shares_outstanding, dividends_per_share, weighted_average_diluted_shares, eps_basic. Ratios: gross_margin, operating_margin, net_margin, return_on_equity, liabilities_to_equity, long_term_debt_to_equity, revenue_growth; any metric's year-over-year change as <metric>_growth, e.g. eps_diluted_growth.
periodsNoNewest annual period groups per issuer; default 1, maximum 20.
tickersYes1 to 20 comma-separated tickers, e.g. MSFT,GOOGL,AMZN (a list of strings is also accepted)
quartersNoNewest fiscal quarters to return in quarterly, newest first (up to 12).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / period
      Added value: +{
+  "description": "quarterly returns the newest 8 fiscal quarters (or as many as fit) unless quarters is given; annual is the default.",
+  "enum": [
+    "annual",
+    "quarterly"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / quarters
      Added value: +{
+  "description": "Newest fiscal quarters to return in quarterly, newest first (up to 12).",
+  "maximum": 12,
+  "minimum": 1,
+  "type": "integer"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / metrics / description
      Previous value: -"Comma-separated metric keys, e.g. revenue,operating_income,capex,free_cash_flow; omitted means all. Keys: revenue, cost_of_revenue, gross_profit, research_and_development, operating_income, depreciation_and_amortization, ebitda (derived), net_income, eps_diluted, total_assets, total_liabilities, long_term_debt, stockholders_equity, cash_and_equivalents, operating_cash_flow, capex, free_cash_flow (derived), share_repurchases, dividends_paid, shares_outstanding, dividends_per_share, weighted_average_diluted_shares, eps_basic."New value: +"Comma-separated metric or ratio keys, e.g. revenue,operating_margin,free_cash_flow; omitted means all metrics and ratios. A ratio brings its inputs with it. Metrics: revenue, cost_of_revenue, gross_profit, research_and_development, operating_income, depreciation_and_amortization, ebitda (derived), net_income, eps_diluted, total_assets, total_liabilities, long_term_debt, stockholders_equity, cash_and_equivalents, operating_cash_flow, capex, free_cash_flow (derived), share_repurchases, dividends_paid, shares_outstanding, dividends_per_share, weighted_average_diluted_shares, eps_basic. Ratios: gross_margin, operating_margin, net_margin, return_on_equity, liabilities_to_equity, long_term_debt_to_equity, revenue_growth; any metric's year-over-year change as <metric>_growth, e.g. eps_diluted_growth."
    • changedInput schema / properties / tickers / description
      Previous value: -"1 to 20 comma-separated tickers, e.g. MSFT,GOOGL,AMZN"New value: +"1 to 20 comma-separated tickers, e.g. MSFT,GOOGL,AMZN (a list of strings is also accepted)"
  3. Changed2 schema fields changed
    • changedInput schema / properties / metrics / description
      Previous value: -"Comma-separated canonical metric keys, e.g. revenue,operating_income,capex; omitted means all curated metrics."New value: +"Comma-separated metric keys, e.g. revenue,operating_income,capex,free_cash_flow; omitted means all. Keys: revenue, cost_of_revenue, gross_profit, research_and_development, operating_income, depreciation_and_amortization, ebitda (derived), net_income, eps_diluted, total_assets, total_liabilities, long_term_debt, stockholders_equity, cash_and_equivalents, operating_cash_flow, capex, free_cash_flow (derived), share_repurchases, dividends_paid, shares_outstanding, dividends_per_share, weighted_average_diluted_shares, eps_basic."
    • changedInput schema / properties / tickers / description
      Previous value: -"1–20 comma-separated tickers, e.g. MSFT,GOOGL,AMZN"New value: +"1 to 20 comma-separated tickers, e.g. MSFT,GOOGL,AMZN"
  4. Added

TDQS

A3.7/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 behavior, so the bar is lower. The description still adds real value by disclosing that unknown tickers yield per-entry errors rather than failing the batch, that each result preserves requested/canonical identity and source lineage, and that point-in-time filtering is unsupported.

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?

Two dense sentences that lead with the core capability and batch limit before the defaults and caveats. Every clause carries information; no filler or repetition of the title.

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?

With no output schema and five parameters, the description does well by covering batch limits, defaults, per-entry error handling, identity/lineage, and the PIT-filtering gap. Only the response shape remains unspecified, which is a minor omission given the params and error semantics are addressed.

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 schema already documents periods, quarters, metrics and the annual/quarterly enum in detail. The description only reinforces the ticker count and default period behavior, adding no syntax or format detail beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (read), resource (annual fundamentals) and scope (1 to 20 comma-separated tickers in one request), and clarifies the batch nature that separates it from the singular get_fundamentals sibling. It never names that sibling explicitly, so the differentiation is inferred rather than stated.

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?

Communicates defaults (one newest period per issuer, all metrics when omitted) and a hard limitation ('No historical point-in-time filtering'), which helps an agent know when this tool is appropriate. It gives no explicit when-to-use vs get_fundamentals routing, so usage is implied rather than guided.

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

All TickerFacts toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources