Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

Financial Statements

financial_statement
Read-onlyIdempotent

Get financial reports for a security by symbol, selecting income statement, balance sheet, or cash flow, and choose annual, semi-annual, or quarterly periods.

Instructions

Get financial statements (income statement, balance sheet, or cash flow) for a security. kind: IS/BS/CF/ALL. report: af (annual, default), saf (semi-annual), qf (quarterly full), q1/q2/q3.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_jqNoOptional 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.
kindNoStatement kind: "IS" (income statement), "BS" (balance sheet), "CF" (cash flow), "ALL" (default)
reportNoReport period: "af" (annual), "saf" (semi-annual), "qf" (quarterly full), "q1"/"q2"/"q3"
symbolYesSecurity symbol, e.g. "AAPL.US"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.0
    • 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."
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "FinancialReportField": {
-      "properties": {
-        "display_order": {
-          "format": "int32",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "field": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "level": {
-          "format": "int32",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "value": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "value_type": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "yoy": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "FinancialStatementKind": {
-      "properties": {
-        "currency": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "empty_fields": {
-          "items": {
-            "type": "string"
-          },
-          "type": [
-            "array",
-            "null"
-          ]
-        },
-        "list": {
-          "items": {
-            "$ref": "#/$defs/FinancialStatementPeriod"
-          },
-          "type": [
-            "array",
-            "null"
-          ]
-        },
-        "report": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "FinancialStatementPeriod": {
-      "properties": {
-        "ff_period": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "ff_year": {
-          "format": "int32",
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "fields": {
-          "items": {
-            "$ref": "#/$defs/FinancialReportField"
-          },
-          "type": [
-            "array",
-            "null"
-          ]
-        },
-        "fp_end": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "report_txt": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "rpt_date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "balance_sheet": {
-      "anyOf": [
-        {
-          "$ref": "#/$defs/FinancialStatementKind"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "cash_flow": {
-      "anyOf": [
-        {
-          "$ref": "#/$defs/FinancialStatementKind"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "currency": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "empty_fields": {
-      "items": {
-        "type": "string"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    },
-    "income_statement": {
-      "anyOf": [
-        {
-          "$ref": "#/$defs/FinancialStatementKind"
-        },
-        {
-          "type": "null"
-        }
-      ]
-    },
-    "list": {
-      "items": {
-        "$ref": "#/$defs/FinancialStatementPeriod"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    },
-    "report": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.8.4
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "FinancialReportField": {
+      "properties": {
+        "display_order": {
+          "format": "int32",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "field": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "level": {
+          "format": "int32",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "name": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "value": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "value_type": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "yoy": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "FinancialStatementKind": {
+      "properties": {
+        "currency": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "empty_fields": {
+          "items": {
+            "type": "string"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        },
+        "list": {
+          "items": {
+            "$ref": "#/$defs/FinancialStatementPeriod"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        },
+        "report": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "FinancialStatementPeriod": {
+      "properties": {
+        "ff_period": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "ff_year": {
+          "format": "int32",
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "fields": {
+          "items": {
+            "$ref": "#/$defs/FinancialReportField"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        },
+        "fp_end": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "report_txt": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "rpt_date": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "properties": {
+    "balance_sheet": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/FinancialStatementKind"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "cash_flow": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/FinancialStatementKind"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "currency": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "empty_fields": {
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "income_statement": {
+      "anyOf": [
+        {
+          "$ref": "#/$defs/FinancialStatementKind"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "list": {
+      "items": {
+        "$ref": "#/$defs/FinancialStatementPeriod"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "report": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  4. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"FinancialStatementParam"
  5. Addedv0.4.5
  6. Removedv0.4.0
  7. Addedv0.3.2
  8. Removedv0.3.1
  9. Addedv0.2.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already disclose that this is read-only, idempotent, and non-destructive. The description adds the supported statement kinds and report periods, which is useful scoping context. It does not describe response shape, pagination, rate limits, or the behavior of the ALL option, but it does not contradict the annotations.

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?

The description is two compact sentences with the purpose front-loaded and no filler. The parameter quick-reference is dense but immediately useful. It earns its place despite some overlap with the schema.

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?

The core invocation details are present: required symbol, kind values, report values, and defaults. However, with no output schema, the description does not clarify the shape of the response or what ALL returns. It also lacks disambiguation from closely related sibling tools, making the context adequate but not complete.

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 coverage is 100%, so the schema already documents kind, report, symbol, and _jq. The description largely restates the kind/report enums and adds that 'af' is the default report, which is a minor increment. This is a baseline-3 situation where the schema carries the parameter-documentation burden.

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 says 'Get financial statements (income statement, balance sheet, or cash flow) for a security,' which is a specific verb and resource. It clearly identifies what the tool returns. However, it does not differentiate this tool from nearby siblings such as financial_report, cash_flow, or statement_export.

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 guidance about when to use financial_statement versus related alternatives like financial_report, financial_report_snapshot, cash_flow, or statement_export. The only implicit guidance is that it is relevant when financial statements are requested. No exclusions, prerequisites, or alternative-selection conditions are stated.

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

Deploy Server

Other Tools