Skip to main content
Glama

Annalist Financial Statements

Get the values of a company over time

get_series
Read-onlyIdempotent

The values of one company over time: items of its statements and ratios together (measures: revenue, net_income, total_assets, cfo, corp.operating_margin, roic), a whole statement (statement: income_statement, balance_sheet, cash_flow) or a category of ratios. frequency is quarterly, annual, ttm (ratios over the last 4 quarters) or quarter_end; from and to are fiscal periods or ISO dates; at gives the snapshot that was the latest on a date. Each value comes with its unit, method and source documents, a ratio with the documents of the figures it is computed from. A page holds the latest periods and next gives the earlier ones; not_included names what is left out, such as the quarters of a company that reports fiscal years only.

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": {
      "company": "<company>"
    },
    "name": "get_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNoan ISO date: the snapshot that was the latest on that date, in place of the latest snapshot
toNolast period, in the same forms
fromNofirst period: a fiscal year (2024), a fiscal quarter (FY2024 Q2) or an ISO date
limitNoperiods in one page (default 12)
cursorNothe next of an earlier answer, for the next page of the same call
compactNovalues and units only, without definitions, methods and documents
companyYesthe company of a search result (apple), or a ticker or CIK
categoryNoevery ratio of one category, for example Credit metrics or Profitability
measuresNoitem keys, item labels or ratio ids or short names
frequencyNodefault: quarters where the company reports them, ttm for ratios
statementNoevery item of one statement

Output Schema

NameRequiredDescriptionDefault
nameNo
nextNo
as_ofNo
countYes
firstNo
seriesYes
companyYes
reportsNo
citationNo
completeYes
returnedNo
snapshotYes
conventionsNo
not_includedYes
latest_periodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely non-obvious behavior: pages hold the latest periods and "next" walks backwards, "not_included" reports omitted data such as quarters for fiscal-year-only reporters, and each value carries unit, method, and source documents. That is substantial disclosure beyond the annotations; only error behavior is unaddressed.

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 purpose is front-loaded in the opening clause and almost every phrase carries information (mode list, frequency semantics, pagination, not_included). However, it is compressed into two very dense sentences with nested parentheses, which makes it harder to scan than a short structured list would be.

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?

Given 11 parameters at full schema coverage and an output schema, the description need not restate return fields, yet it still explains pagination direction, the snapshot parameter, and data-exclusion reporting. For a high-complexity query tool it is close to complete; only failure modes and any cost/rate considerations are absent.

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 the baseline is 3, but the description earns more: it defines ttm as ratios over the last four quarters, explains that from/to accept fiscal periods or ISO dates, and clarifies that "at" selects the snapshot that was latest on a date. Those are semantic clarifications that the schema fields only gesture at.

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?

The definition states a concrete verb and resource ("the values of one company over time") and enumerates the three retrieval modes: measures, a whole statement, or a ratio category. It implicitly separates itself from compare_companies by emphasizing "one company", but never names a sibling, so the differentiation is left to inference.

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?

Usage is implied by the mode enumeration (pick measures, statement, or category) and by the frequency defaults, but there is no explicit when-to-use/when-not statement and no pointer to alternatives such as get_company for a single snapshot or compare_companies for cross-company work. The agent must infer routing from sibling names alone.

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