Skip to main content
Glama

AIsa Equities

Get Cash Flow Statements

get_financial_financials_cash_flow_statements
Read-onlyIdempotent

Get cash flow statements for a ticker.

Published reference price: $0.02 USD per successful request. Account-specific pricing and final settlement may differ.

Input Schema

NameRequiredDescriptionDefault
cikNoThe Central Index Key (CIK) of the company.
isinNoThe ISIN (International Securities Identification Number) of a non-US listing. An alternative to `ticker` and `market`.
limitNoThe maximum number of cash flow statements to return. This is the total across all pages, not a page size: each page holds up to 10 records, linked by `next_page_url`.
cursorNoOpaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.
marketNoThe market the company is listed in: `US` (the default), `UK` or `FR`. Any ticker of the company, including a second share class, returns the company's statements.
periodYesThe time period of the cash flow statements.
tickerNoThe ticker symbol. Required if cik or isin is not provided.
exchangeNoDeprecated alias of `market`: `LSE` means `market=UK`. Existing requests keep working. France has no alias: name it with `market=FR`.
filing_dateNoFilter by exact SEC filing date in YYYY-MM-DD format. Rows without a known filing date are excluded.
report_periodNoFilter by exact report period date in YYYY-MM-DD format.
filing_date_gtNoFilter by SEC filing date greater than date in YYYY-MM-DD format. Rows without a known filing date are excluded.
filing_date_ltNoFilter by SEC filing date less than date in YYYY-MM-DD format. Rows without a known filing date are excluded.
filing_date_gteNoFilter by SEC filing date greater than or equal to date in YYYY-MM-DD format. Rows without a known filing date are excluded.
filing_date_lteNoFilter by SEC filing date less than or equal to date in YYYY-MM-DD format. Useful for point-in-time queries: returns only data that was publicly filed by the given date. Rows without a known filing date are excluded.
report_period_gtNoFilter by report period greater than date in YYYY-MM-DD format.
report_period_ltNoFilter by report period less than date in YYYY-MM-DD format.
report_period_gteNoFilter by report period greater than or equal to date in YYYY-MM-DD format.
report_period_lteNoFilter by report period less than or equal to date in YYYY-MM-DD format.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / exchange / description
      Previous value: -"The exchange the ticker is listed on. Omit for US listings. Use `LSE` for the London Stock Exchange; any ticker of the company, including a second share class, returns the company's statements."New value: +"Deprecated alias of `market`: `LSE` means `market=UK`. Existing requests keep working. France has no alias: name it with `market=FR`."
    • removedInput schema / properties / exchange / enum
      Removed value: -[
      -  "LSE"
      -]
    • changedInput schema / properties / isin / description
      Previous value: -"The ISIN (International Securities Identification Number) of a non-US listing. An alternative to `ticker` and `exchange`."New value: +"The ISIN (International Securities Identification Number) of a non-US listing. An alternative to `ticker` and `market`."
    • addedInput schema / properties / market
      Added value: +{
      +  "description": "The market the company is listed in: `US` (the default), `UK` or `FR`. Any ticker of the company, including a second share class, returns the company's statements.",
      +  "enum": [
      +    "US",
      +    "UK",
      +    "FR"
      +  ],
      +  "type": "string"
      +}
  2. Changed10 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "Opaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.",
      +  "type": "string"
      +}
    • addedInput schema / properties / exchange
      Added value: +{
      +  "description": "The exchange the ticker is listed on. Omit for US listings. Use `LSE` for the London Stock Exchange; any ticker of the company, including a second share class, returns the company's statements.",
      +  "enum": [
      +    "LSE"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / filing_date
      Added value: +{
      +  "description": "Filter by exact SEC filing date in YYYY-MM-DD format. Rows without a known filing date are excluded.",
      +  "format": "date",
      +  "type": "string"
      +}
    • addedInput schema / properties / filing_date_gt
      Added value: +{
      +  "description": "Filter by SEC filing date greater than date in YYYY-MM-DD format. Rows without a known filing date are excluded.",
      +  "format": "date",
      +  "type": "string"
      +}
    • addedInput schema / properties / filing_date_gte
      Added value: +{
      +  "description": "Filter by SEC filing date greater than or equal to date in YYYY-MM-DD format. Rows without a known filing date are excluded.",
      +  "format": "date",
      +  "type": "string"
      +}
    • addedInput schema / properties / filing_date_lt
      Added value: +{
      +  "description": "Filter by SEC filing date less than date in YYYY-MM-DD format. Rows without a known filing date are excluded.",
      +  "format": "date",
      +  "type": "string"
      +}
    • addedInput schema / properties / filing_date_lte
      Added value: +{
      +  "description": "Filter by SEC filing date less than or equal to date in YYYY-MM-DD format. Useful for point-in-time queries: returns only data that was publicly filed by the given date. Rows without a known filing date are excluded.",
      +  "format": "date",
      +  "type": "string"
      +}
    • addedInput schema / properties / isin
      Added value: +{
      +  "description": "The ISIN (International Securities Identification Number) of a non-US listing. An alternative to `ticker` and `exchange`.",
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"The maximum number of cash flow statements to return."New value: +"The maximum number of cash flow statements to return. This is the total across all pages, not a page size: each page holds up to 10 records, linked by `next_page_url`."
    • changedInput schema / properties / ticker / description
      Previous value: -"The ticker symbol. Required if cik is not provided."New value: +"The ticker symbol. Required if cik or isin is not provided."
  3. Changed7 schema fields changed
    • removedInput schema / properties / cursor
      Removed value: -{
      -  "description": "Opaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.",
      -  "type": "string"
      -}
    • removedInput schema / properties / filing_date
      Removed value: -{
      -  "description": "Filter by exact SEC filing date in YYYY-MM-DD format. Rows without a known filing date are excluded.",
      -  "format": "date",
      -  "type": "string"
      -}
    • removedInput schema / properties / filing_date_gt
      Removed value: -{
      -  "description": "Filter by SEC filing date greater than date in YYYY-MM-DD format. Rows without a known filing date are excluded.",
      -  "format": "date",
      -  "type": "string"
      -}
    • removedInput schema / properties / filing_date_gte
      Removed value: -{
      -  "description": "Filter by SEC filing date greater than or equal to date in YYYY-MM-DD format. Rows without a known filing date are excluded.",
      -  "format": "date",
      -  "type": "string"
      -}
    • removedInput schema / properties / filing_date_lt
      Removed value: -{
      -  "description": "Filter by SEC filing date less than date in YYYY-MM-DD format. Rows without a known filing date are excluded.",
      -  "format": "date",
      -  "type": "string"
      -}
    • removedInput schema / properties / filing_date_lte
      Removed value: -{
      -  "description": "Filter by SEC filing date less than or equal to date in YYYY-MM-DD format. Useful for point-in-time queries: returns only data that was publicly filed by the given date. Rows without a known filing date are excluded.",
      -  "format": "date",
      -  "type": "string"
      -}
    • changedInput schema / properties / limit / description
      Previous value: -"The maximum number of cash flow statements to return. This is the total across all pages, not a page size: each page holds up to 10 records, linked by `next_page_url`."New value: +"The maximum number of cash flow statements to return."
  4. Changed7 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "Opaque pagination cursor from a previous response's next_page_url. When provided, all other query parameters are ignored: the cursor carries the original request's filters. Treat it as opaque; do not construct or modify it.",
      +  "type": "string"
      +}
    • addedInput schema / properties / filing_date
      Added value: +{
      +  "description": "Filter by exact SEC filing date in YYYY-MM-DD format. Rows without a known filing date are excluded.",
      +  "format": "date",
      +  "type": "string"
      +}
    • addedInput schema / properties / filing_date_gt
      Added value: +{
      +  "description": "Filter by SEC filing date greater than date in YYYY-MM-DD format. Rows without a known filing date are excluded.",
      +  "format": "date",
      +  "type": "string"
      +}
    • addedInput schema / properties / filing_date_gte
      Added value: +{
      +  "description": "Filter by SEC filing date greater than or equal to date in YYYY-MM-DD format. Rows without a known filing date are excluded.",
      +  "format": "date",
      +  "type": "string"
      +}
    • addedInput schema / properties / filing_date_lt
      Added value: +{
      +  "description": "Filter by SEC filing date less than date in YYYY-MM-DD format. Rows without a known filing date are excluded.",
      +  "format": "date",
      +  "type": "string"
      +}
    • addedInput schema / properties / filing_date_lte
      Added value: +{
      +  "description": "Filter by SEC filing date less than or equal to date in YYYY-MM-DD format. Useful for point-in-time queries: returns only data that was publicly filed by the given date. Rows without a known filing date are excluded.",
      +  "format": "date",
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"The maximum number of cash flow statements to return."New value: +"The maximum number of cash flow statements to return. This is the total across all pages, not a page size: each page holds up to 10 records, linked by `next_page_url`."
  5. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and idempotency are covered structurally. The description's only added context is the $0.02 per-successful-request price, which is genuinely useful for an agent but says nothing about pagination, coverage of markets, or data vintage.

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?

A single functional sentence, front-loaded and free of padding. The embedded HTML comment block for pricing is boilerplate noise but does not bloat the prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full schema and an output schema, the description need not explain parameters or returns. What is missing is selection guidance in a crowded family of financial-statement tools, plus any note that a period is mandatory.

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 every one of the 18 parameters is documented in the schema, giving a baseline of 3. "For a ticker" marginally narrows what the schema allows (cik/isin are valid alternatives) and the required `period` parameter is never mentioned in the description.

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?

"Get cash flow statements" is a specific verb+resource and the ticker anchor is clear. It fails to distinguish itself from the sibling tools get_financial_financials_income_statements and get_financial_financials_balance_sheets, which an agent must choose between.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No indication of when to use cash flow statements rather than the income statement, balance sheet, or the generic get_financial_financials endpoint. The choice among these near-identical siblings is left entirely to inference from the tool name.

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