longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Latest Financial Report

financial_report_latest

Read-onlyIdempotent

Get the most recent financial report summary for any security to review key financials.

Instructions

Get the latest financial report summary for a security.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`_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.
`symbol`	Yes	Security symbol, e.g. "700.HK". Use the canonical form — a padded code like "00700.HK" returns an empty record, not an error.

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."

changedInput schema / properties / symbol / description

Previous value: -"Security symbol, e.g. \"700.HK\""New value: +"Security symbol, e.g. \"700.HK\". Use the canonical form — a padded code like \"00700.HK\" returns an empty record, not an error."

Changed2 schema fields changedv0.10.6Sep 10, 2026

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

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "eps": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "gross_margin": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "net_income": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "period": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "report_date": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "revenue": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "roe": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.7.1Jun 26, 2026
- removedInput schema / title
```
Removed value: -"SymbolParam"
```
Changed10 schema fields changedv0.6.0Jun 26, 2026
- removedOutput schema / $schema
```
Removed value: -"https://json-schema.org/draft/2020-12/schema"
```
- removedOutput schema / description
```
Removed value: -"Returned by `financial_report_latest`. Latest financial report summary.\n\nSubset of documented fields; upstream may return more."
```
- removedOutput schema / properties / eps / description
```
Removed value: -"Earnings per share."
```
- removedOutput schema / properties / gross_margin / description
```
Removed value: -"Gross margin."
```
- removedOutput schema / properties / net_income / description
```
Removed value: -"Net income."
```
- removedOutput schema / properties / period / description
```
Removed value: -"Reporting period."
```
- removedOutput schema / properties / report_date / description
```
Removed value: -"Report date."
```
- removedOutput schema / properties / revenue / description
```
Removed value: -"Revenue."
```
- removedOutput schema / properties / roe / description
```
Removed value: -"Return on equity."
```
- removedOutput schema / title
```
Removed value: -"FinancialReportLatestResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `financial_report_latest`. Latest financial report summary.\n\nSubset of documented fields; upstream may return more.",
+  "properties": {
+    "eps": {
+      "description": "Earnings per share.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "gross_margin": {
+      "description": "Gross margin.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "net_income": {
+      "description": "Net income.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "period": {
+      "description": "Reporting period.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "report_date": {
+      "description": "Report date.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "revenue": {
+      "description": "Revenue.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "roe": {
+      "description": "Return on equity.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "title": "FinancialReportLatestResponse",
+  "type": "object"
+}

Addedv0.4.5May 28, 2026
Removedv0.4.0May 21, 2026
Addedv0.3.2May 19, 2026
Removedv0.3.1May 15, 2026
Addedv0.2.1May 9, 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=true, idempotentHint=true, and destructiveHint=false, and the description adds no behavioral context beyond a generic 'Get'. It does not clarify what 'latest' means, what the summary contains, or that a non-canonical symbol returns an empty record; that last detail lives only in the schema.

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 single, concise sentence with no filler and the action is front-loaded. It is efficient, though it slightly repeats the title rather than adding richer context.

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?

For a simple read-only tool with fully documented parameters and safe annotations, the minimal description is arguably sufficient. However, without an output schema and with sibling tools that overlap in purpose, the lack of additional context about return shape and tool selection leaves a noticeable 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%, so the baseline is 3. The description itself adds no parameter meaning, but the schema already fully documents symbol's canonical-form behavior and the generic _jq filter, so no significant gap exists.

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?

The description states a specific verb ('Get'), a concrete resource ('latest financial report summary'), and the scope ('for a security'). However, it does not distinguish this tool from siblings like financial_report, financial_report_snapshot, or financial_report_key_metrics, so the clarity is good but not excellent.

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 mention of alternatives, and no exclusions. Given the large sibling set containing several closely related financial-report tools, an agent receives no help selecting this tool over those alternatives.

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

Deploy Server

Latest Financial Report

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools