longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Financial Report Snapshot

financial_report_snapshot

Read-onlyIdempotent

Get a financial report snapshot with a text summary, actual vs forecast revenue/EBIT/EPS, and financial ratios like ROE and margins. Provide symbol, report type, and fiscal period.

Instructions

Get financial report snapshot: report_desc (text summary), fo_revenue/fo_ebit/fo_eps (actual vs forecast with yoy/cmp), fr_* financial ratios (ROE, margins, assets, cash flow). report: qf/saf/af.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "financial_report_snapshot"
  }
}

Input Schema

Name	Required	Description
`_jq`	No	Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data \| map({symbol}). Omit for the full response.
`report`	No	Report type: "qf" (quarterly), "saf" (semi-annual), "af" (annual)
`symbol`	Yes	Security symbol, e.g. "AAPL.US"
`fiscal_year`	No	Fiscal year, e.g. 2024
`fiscal_period`	No	Fiscal period, e.g. "1" "2" "3" "4"

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.12.0Sep 23, 2026

addedInput schema / properties / _jq / description

Added value: +"Optional jq filter (jaq syntax) applied to this tool's JSON response before it is returned; it never changes the upstream request. One output is returned as-is, several as a JSON array, none as []. Module imports and the `env`/`debug`/`stderr` builtins are unavailable. Example: .data | map({symbol}). Omit for the full response."

removedInput schema / properties / fiscal_year / format
```
Removed value: -"uint32"
```

Changed2 schema fields changedv0.10.6Sep 10, 2026

addedInput schema / properties / _jq
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / (root)

Previous value: -{
-  "$defs": {
-    "ForecastActual": {
-      "properties": {
-        "cmp": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "yoy": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "fo_ebit": {
-      "anyOf": [
-        {
-          "$ref": "#/$defs/ForecastActual"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "fo_eps": {
-      "anyOf": [
-        {
-          "$ref": "#/$defs/ForecastActual"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "fo_revenue": {
-      "anyOf": [
-        {
-          "$ref": "#/$defs/ForecastActual"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "report_desc": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"FinancialReportSnapshotParam"
```

Changed10 schema fields changedv0.6.0Jun 26, 2026

removedOutput schema / $defs / ForecastActual / description

Removed value: -"An actual-vs-forecast comparison block in `financial_report_snapshot`\n(`fo_revenue` / `fo_ebit` / `fo_eps`).\n\nSubset of documented fields; upstream may return more."

removedOutput schema / $defs / ForecastActual / properties / cmp / description
```
Removed value: -"Actual vs forecast comparison."
```
removedOutput schema / $defs / ForecastActual / properties / yoy / description
```
Removed value: -"Year-over-year change."
```

removedOutput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

removedOutput schema / description

Removed value: -"Returned by `financial_report_snapshot`. Actual-vs-forecast comparison\nplus financial ratios.\n\nSubset of documented fields; upstream may return more."

removedOutput schema / properties / fo_ebit / description
```
Removed value: -"EBIT: actual vs forecast."
```
removedOutput schema / properties / fo_eps / description
```
Removed value: -"EPS: actual vs forecast."
```
removedOutput schema / properties / fo_revenue / description
```
Removed value: -"Revenue: actual vs forecast."
```
removedOutput schema / properties / report_desc / description
```
Removed value: -"Text summary of the report."
```

removedOutput schema / title

Removed value: -"FinancialReportSnapshotResponse"

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "ForecastActual": {
+      "description": "An actual-vs-forecast comparison block in `financial_report_snapshot`\n(`fo_revenue` / `fo_ebit` / `fo_eps`).\n\nSubset of documented fields; upstream may return more.",
+      "properties": {
+        "cmp": {
+          "description": "Actual vs forecast comparison.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "yoy": {
+          "description": "Year-over-year change.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `financial_report_snapshot`. Actual-vs-forecast comparison\nplus financial ratios.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "fo_ebit": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/ForecastActual"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "EBIT: actual vs forecast."
+    },
+    "fo_eps": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/ForecastActual"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "EPS: actual vs forecast."
+    },
+    "fo_revenue": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/ForecastActual"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Revenue: actual vs forecast."
+    },
+    "report_desc": {
+      "description": "Text summary of the report.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "title": "FinancialReportSnapshotResponse",
+  "type": "object"
+}

Addedv0.4.5May 28, 2026
Removedv0.4.0May 21, 2026
Addedv0.3.2May 19, 2026
Removedv0.3.1May 15, 2026
Addedv0.3.0May 15, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value by listing return field groups, but does not discuss auth requirements, rate limits, or response shape (no output schema). With annotations covering most behavioral expectations, a 3 is appropriate for the modest extra context.

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 description is a compact single sentence that front-loads the main action and then lists the key field groups and report types. It avoids redundancy and every clause contributes meaning, though it might be slightly dense for an agent to parse quickly.

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?

For a snapshot tool with rich annotations (safe, idempotent, read-only), the description covers the core return fields and report types. No output schema exists, but the listed fields give sufficient context for an agent to decide whether this tool provides the needed data. Minor gaps like pagination or filter behavior are not critical for a snapshot.

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 all five parameters (symbol, report, fiscal_year, fiscal_period, _jq) are documented in the schema. The description's mention of report types ('qf/saf/af') and field groups adds only marginal semantic value beyond what the schema already provides; baseline 3 is correct.

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?

The description states a specific verb ('Get') and resource ('financial report snapshot'), enumerates the exact field groups returned (report_desc, fo_revenue/fo_ebit/fo_eps, fr_* ratios), and clarifies report types (qf/saf/af). This distinguishes it from siblings like financial_report, financial_report_key_metrics, and financial_statement by the snapshot's condensed nature and the specific metrics.

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

Usage Guidelines3/5

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

The description implies usage by naming the report types and field categories, but it does not explicitly state when to prefer this tool over alternatives (e.g., financial_report_latest for the most recent data, financial_report_key_metrics for ratios only). No when-not or alternative-selection guidance is provided beyond the tool's inherent scope.

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

Deploy Server