Skip to main content
Glama

MetricDuck — Financial Analysis

by com.metricduck
OverviewDiscussionsAdmin

Financial Statements

get_financials
Read-only

Get multi-period financial statements: income statement, balance sheet, and cash flow in one call.

Returns quantitative historical data with key metrics and trends. Default: all 3 statements, quarterly, 2 years. For qualitative analysis (risks, accounting quality, management tone), use get_filing_index (signal map) then get_filing_section to read the text.

Use Cases:

  • "Show me AAPL's financials" -> all statements

  • "MSFT revenue trend 5 years" -> period="annual", years=5

  • "Is Tesla's debt increasing?" -> statements=["balance"]

  • "As of a past date / point-in-time" -> get_financials("MSFT", vantage_date="2024-04-30")

Each period cites its original disclosing SEC filing (accession + filed date in a footnote; resolvable EDGAR index handles in the <raw_data> block), so every figure is traceable to its source filing.

Exactness: the markdown table ABBREVIATES ($68.14M) — it quantises to $10K above $1M and $10M above $1B, so it is not a tie-out surface. The <raw_data> block carries the exact stored value (68135000). Quote figures from <raw_data>, not the table, whenever the precise number matters.

Responses capped at ~20K chars. If truncated, whole statements are dropped (not sliced) with a note — request fewer statements or reduce years. Note the cap also trims <raw_data> periods, so a truncated response can lose the exact channel for the dropped periods.

Company-reported Adjusted EBITDA (issuer-specific add-backs) is NOT a computed metric here — read the issuer's own reconciliation via get_filing_section (earnings release / MD&A).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearsNoYears of history (default 2, max 10)
periodNoTime period granularityquarterly
tickerYesCompany ticker symbol (e.g., 'AAPL'). Must be exact.
statementsNoWhich statements to include (default: all three)
vantage_dateNoAs-of vantage (YYYY-MM-DD): restrict to filings PUBLISHED on or before this date, and cite the filing that was current then. Omit for the latest. IMPORTANT — this bounds which FILINGS are visible and which SOURCE is cited; it does NOT reconstruct the value as it stood on that date. If a later filing restated a period, THE RESTATED VALUE IS WHAT IS SERVED under a pre-vantage citation — and the response carries an explicit LOOK-AHEAD warning naming the affected periods, so the exposure is disclosed rather than silent. For a true as-originally-filed series use get_xbrl_facts with period_history=true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover readOnly/openWorld, but the description adds substantial non-obvious behavior: the markdown table is quantised/abbreviated while <raw_data> holds exact values, the ~20K char cap drops whole statements, and vantage_date does NOT reconstruct point-in-time values because restated figures carry a look-ahead warning. These are exactly the operating hazards 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?

Front-loaded with purpose and defaults, then layered with caveats; every section (exactness, truncation, adjusted EBITDA) carries distinct information. It is long, and the vantage_date warning duplicates part of the schema description, but no sentence is purely filler.

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 no output schema and five parameters, the description compensates by explaining return shape (markdown tables plus <raw_data> block, per-period filing citations with accession and filed date) and truncation behavior. Nothing an agent needs in order to call and interpret this tool is missing.

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 would be 3; the description goes further by tying parameter values to concrete outcomes (defaults of all three statements / quarterly / 2 years) and by explaining the look-ahead semantics of vantage_date beyond the schema's own note, plus the Adjusted EBITDA caveat. It does not add syntax detail for years/period beyond the schema.

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?

States a specific verb and resource ('Get multi-period financial statements: income statement, balance sheet, and cash flow in one call') and explicitly distinguishes itself from get_filing_index/get_filing_section for qualitative work, setting the boundary of its scope. An agent can pick it out from the ~22 siblings immediately.

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?

Provides explicit when-to-use guidance plus four natural-language use cases that map directly onto parameter combinations (annual/years=5, statements=['balance'], vantage_date). It also names the alternative tools for qualitative analysis and for true as-originally-filed series (get_xbrl_facts with period_history=true), so both the use and the non-use case are covered.

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

All MetricDuck — Financial Analysis 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