AIsa Equities

Get Financial Metrics Snapshot

get_financial_financial_metrics_snapshot

Read-onlyIdempotent

Get the real-time financial metrics snapshot for a stock, including valuation ratios, 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_financial_financial_metrics_snapshot"
  }
}

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 `market`.
`market`	No	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 metrics. Price-based values (market cap, enterprise value, valuation ratios, dividend yield) are not yet available for UK tickers.
`ticker`	No	The ticker symbol of the company.
`exchange`	No	Deprecated alias of `market`: `LSE` means `market=UK`. Existing requests keep working. France has no alias: name it with `market=FR`.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 1, 2026

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 metrics. Price-based values (market cap, enterprise value, valuation ratios, dividend yield) are not yet available for UK tickers."New value: +"Deprecated alias of `market`: `LSE` means `market=UK`. Existing requests keep working. France has no alias: name it with `market=FR`."

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 / description

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

Changed1 schema field changedOct 20, 2026

addedInput schema / properties / market

Added value: +{
+  "enum": [
+    "UK",
+    "US"
+  ],
+  "type": "string"
+}

Changed4 schema fields changedOct 19, 2026

addedInput schema / properties / cik

Added value: +{
+  "description": "The Central Index Key (CIK) of the company. Can be used instead of ticker.",
+  "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 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"
+}

addedInput schema / properties / ticker / description
```
Added value: +"The ticker symbol of the company."
```

Changed2 schema fields changedOct 15, 2026

removedInput schema / properties / cik

Removed value: -{
-  "description": "The Central Index Key (CIK) of the company. Can be used instead of ticker.",
-  "type": "string"
-}

removedInput schema / properties / ticker / description
```
Removed value: -"The ticker symbol of the company."
```

Changed2 schema fields changedOct 15, 2026

addedInput schema / properties / cik

Added value: +{
+  "description": "The Central Index Key (CIK) of the company. Can be used instead of ticker.",
+  "type": "string"
+}

addedInput schema / properties / ticker / description
```
Added value: +"The ticker symbol of the company."
```

Changed2 schema fields changedOct 15, 2026

removedInput schema / properties / cik

Removed value: -{
-  "description": "The Central Index Key (CIK) of the company. Can be used instead of ticker.",
-  "type": "string"
-}

removedInput schema / properties / ticker / description
```
Removed value: -"The ticker symbol of the company."
```

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 readOnly, idempotent, openWorld, and non-destructive behavior, so the safety profile is covered. The description adds a genuine behavioral fact beyond the annotations – a published $0.02 per-successful-request price – but says nothing about data freshness/latency for a 'real-time' snapshot or any eligibility restrictions.

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 functional sentence is front-loaded and single-purpose. The long adjective list of metric families is mildly padded and the injected pricing block adds bulk, but neither obscures the core statement.

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?

With full schema coverage, a complete annotation set, and an output schema, the description carries only the burden of stating what the tool returns at a high level, which it does. Nothing an agent needs to invoke it is missing, though a note on freshness or on choosing between identifier parameters in the description would round it out.

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%, and the schema itself explains cik vs ticker vs isin vs market, including the UK/FR caveats and the deprecated exchange alias. 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?

States a specific verb (Get) and resource (real-time financial metrics snapshot for a stock) and enumerates the metric families returned (valuation, profitability, efficiency, liquidity, leverage, growth, per share). An agent can distinguish this from the statement-oriented siblings like get_financial_financials_income_statements, though it never explicitly contrasts with get_financial_financial_metrics.

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 / when-not-to-use guidance and no mention of prerequisites such as needing a ticker, CIK, or ISIN. The closest thing to routing is the word 'real-time', which implicitly distinguishes it from the historical get_financial_financial_metrics sibling, but that distinction is never stated.

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?