AIsa Equities

Get Financial Statements

get_financial_financials

Read-onlyIdempotent

Get all financial statements for a ticker.

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

Input Schema

Name	Required	Description
`cik`	No	The Central Index Key (CIK) of the company.
`isin`	No	The ISIN (International Securities Identification Number) of a non-US listing. An alternative to `ticker` and `exchange`.
`limit`	No	The maximum number of financial 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`.
`cursor`	No	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.
`period`	Yes	The time period of the financial statements.
`ticker`	No	The ticker symbol. Required if cik or isin is not provided.
`exchange`	No	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.
`filing_date`	No	Filter by exact SEC filing date in YYYY-MM-DD format. Rows without a known filing date are excluded.
`report_period`	No	Filter by exact report period date in YYYY-MM-DD format.
`filing_date_gt`	No	Filter by SEC filing date greater than date in YYYY-MM-DD format. Rows without a known filing date are excluded.
`filing_date_lt`	No	Filter by SEC filing date less than date in YYYY-MM-DD format. Rows without a known filing date are excluded.
`filing_date_gte`	No	Filter 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_lte`	No	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.
`report_period_gt`	No	Filter by report period greater than date in YYYY-MM-DD format.
`report_period_lt`	No	Filter by report period less than date in YYYY-MM-DD format.
`report_period_gte`	No	Filter by report period greater than or equal to date in YYYY-MM-DD format.
`report_period_lte`	No	Filter by report period less than or equal to date in YYYY-MM-DD format.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedOct 15, 2026

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 financial statements to return."New value: +"The maximum number of financial 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."

Changed7 schema fields changedOct 15, 2026

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 financial 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 financial statements to return."

Changed7 schema fields changedOct 15, 2026

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 financial statements to return."New value: +"The maximum number of financial 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`."

First observedSep 15, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds only the per-request pricing note, which is genuinely useful cost context, but says nothing about pagination depth or result volume beyond what the schema already documents.

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 core sentence is tight and front-loaded. The pricing block is relevant but wrapped in decorative HTML comment markers that add noise without content.

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 an output schema and fully documented input schema, the return shape is handled elsewhere. What remains missing is the disambiguation that matters most for a 27-sibling toolset: whether this returns all three statement types, and the effect of `period` on that. Adequate but with a clear gap.

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% across all 17 parameters, including enums, identifier alternatives, cursor opacity, and date-filter semantics, so the schema carries the full burden. The description adds no parameter meaning at all, making 3 the correct baseline.

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 and resource ('Get all financial statements for a ticker'), which reads as the aggregate counterpart to the sibling balance-sheet/income-statement/cash-flow tools. However it never explicitly says it returns all statement types combined, so the distinction from get_financial_financials_balance_sheets et al. must be inferred.

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 when-to-use, when-not-to-use, or named alternative appears. Nothing tells the agent when to pick this aggregate tool over the three per-statement siblings, which is the key routing decision here.

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

All AIsa Equities tools Inspect

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

Need Help?