AIsa Finance

Get Financial Metrics

get_financial_financial_metrics

Read-onlyIdempotent

Get financial metrics for a ticker, including valuation, profitability, efficiency, liquidity, leverage, growth, and per share metrics.

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. Can be used instead of ticker.
`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 results 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 for the financial data.
`ticker`	No	The ticker symbol of the company. Required if cik 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 metrics. Price-based values (market cap, enterprise value, valuation ratios, dividend yield) are not yet available for UK tickers.
`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.

Changed2 schema fields changedOct 19, 2026

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 metrics. Price-based values (market cap, enterprise value, valuation ratios, dividend yield) are not yet available for UK tickers.",
+  "enum": [
+    "LSE"
+  ],
+  "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"
+}

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

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and open-world behavior, so the safety profile is covered externally. The description adds no further behavioral context: nothing about pagination mechanics, the UK-ticker limitation on price-based values, or how many records come back by default (the schema carries pagination, but the description does not reinforce it). The embedded pricing banner is commercial metadata rather than behavioral disclosure.

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 single descriptive sentence is front-loaded and efficient, with the metric families listed in a compact enumeration. The only bloat is the injected pricing comment block, which is boilerplate rather than substance.

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?

An output schema exists, so return structure need not be explained, and annotations cover the safety profile. What is missing is the disambiguation from the snapshot and general financials siblings and any note that periods drive the result shape, which matters for a 17-parameter tool in a dense sibling family.

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 parameter is already documented in the schema, including the CIK/ISIN/ticker lookup alternatives, pagination, and the LSE limitation. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

Specifies a concrete verb and resource ('Get financial metrics for a ticker') and enumerates the metric families returned (valuation, profitability, efficiency, liquidity, leverage, growth, per share), which tells an agent what data is inside. It does not, however, distinguish this tool from close siblings such as get_financial_financial_metrics_snapshot or get_financial_financials, so an agent cannot route between them from the description alone.

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?

There is no when-to-use guidance, no statement of prerequisites (e.g., that ticker or cik must be supplied), and no mention of the snapshot variant that overlaps in name and purpose. The agent must infer applicability entirely from the name and schema.

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?