Skip to main content
Glama

All statements as known on a date

snapshot_as_of
Read-onlyIdempotent

One call that returns the income statement, balance sheet and cash flow statement of a company exactly as FinancialMD knew them on a date: no later restatements, no periods filed afterwards. This is the tool for point-in-time work: backtests, "what did an investor know on the day", reproducing a past model, or checking whether a decision was made on numbers that were later restated. Each statement carries its own meta; a statement the company does not have is reported as an error inside the snapshot rather than failing the whole call. The ratios computed from the same facts as known on that date ride along under ratios.

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": {
      "as_of": "2023-06-30",
      "limit": 4,
      "company": "ticker:AAPL",
      "period_type": "annual"
    },
    "name": "snapshot_as_of"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofYesThe knowledge date to replay (YYYY-MM-DD or RFC 3339). Required.
limitNoMaximum number of periods or items to return (default 5, at most 200).
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_typeNoPeriod basis: annual (fiscal years), quarterly, ltm (last twelve months) or ytd (year to date).annual

Output Schema

NameRequiredDescriptionDefault
dataNoas_of plus one grid per key (income_statement, balance_sheet, cash_flow and ratios: { statement, period_type, view, currency, periods, rows, meta }), or { error } for a grid that is not available.
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.5/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the description's added value is what matters and it delivers: a missing statement is reported as an error inside the snapshot rather than failing the whole call, each statement carries its own meta, and ratios derived from the same point-in-time facts are included under `ratios`. Partial-failure semantics and payload composition are exactly the traits annotations cannot express.

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?

Four dense sentences: purpose and scope first, then the use-case list, then the error-isolation behavior, then the ratios payload. No filler and no restatement of the name or title.

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?

An output schema exists, so return values need not be enumerated, yet the description still flags the two things an agent would otherwise get wrong: partial failure per statement and the presence of a `ratios` block. Combined with annotations covering safety, nothing material for correct invocation is missing.

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%, including the as_of date pattern, the accepted company identifier forms, period_type enum and limit bounds, so the schema carries parameter meaning fully. The description adds nothing parameter-specific beyond the general 'as of a date' framing, which is the expected baseline when the schema does the heavy lifting.

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 set ('returns the income statement, balance sheet and cash flow statement of a company') plus a precise temporal scope ('exactly as FinancialMD knew them on a date: no later restatements, no periods filed afterwards'). That scoping makes it distinguishable from as-reported or standardized financials without needing to open 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 Guidelines4/5

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

It gives explicit when-to-use criteria with four concrete scenarios (backtests, 'what did an investor know on the day', reproducing a past model, checking whether a decision relied on later-restated numbers). It stops short of naming a sibling alternative or stating when not to use it, so routing is clear in the positive direction only.

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