AIsa Finance

Get all financial statements

get_financial_financials

Read-onlyIdempotent

All three statements for one company in a single call. Returns a financials object holding income_statements, balance_sheets and cash_flow_statements, each the same shape the dedicated tools return. period is required (annual, quarterly or ttm); identify the company by ticker or cik and cap with limit. Use it when you need the full picture and would otherwise make three calls. When you only need one statement, get_financial_financials_income_statements, get_financial_financials_balance_sheets or get_financial_financials_cash_flow_statements returns far less data; when you need a handful of named fields across several companies, post_financial_financials_search_line_items is narrower still.

Input Schema

TableJSON Schema

Name	Required	Description
`cik`	No	The Central Index Key (CIK) of the company.
`limit`	No	The maximum number of financial statements to return.
`period`	Yes	The time period of the financial statements.
`ticker`	No	The ticker symbol. Required if cik is not provided.
`report_period`	No	Filter by exact report period date in YYYY-MM-DD format.
`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

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds the return structure (financials object with three arrays, each matching dedicated tool shapes) and clarifies that period is required and company identification via ticker or cik. This enriches behavior beyond annotations without contradiction.

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?

Two sentences with zero waste. The first sentence states purpose and return shape; the second gives usage guidance and alternatives. Information is front-loaded and every sentence earns its place.

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?

Given the presence of an output schema, the 100% schema coverage, and the description covering the primary use case plus alternatives, nothing essential is missing for an agent to call it correctly.

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% with every parameter documented. The description repeats period requirement and ticker/cik usage but adds no new semantic detail beyond what the schema already provides. Baseline 3 applies for high schema coverage.

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 'get' and resource 'all financial statements' (all three for one company), and clearly distinguishes from dedicated statement tools and search line items by naming them. The scope is unambiguous.

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?

Explicitly says when to use it: when you need the full picture and would otherwise make three calls. It also names the alternatives (dedicated statement tools, search line items) and the conditions that select them, leaving no inference.

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

All AIsa Finance 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?