longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Financial Report Key Metrics (US)

financial_report_key_metrics

Read-onlyIdempotent

Retrieve key financial metrics for US-listed symbols, selecting annual, semi-annual, or quarterly report periods to analyze company performance.

Instructions

Get key financial metrics (fin-keyfactor) for a US symbol. report: af (annual, default), saf, qf, q1/q2/q3. US accounts only; errors with DcRegionRestricted for AP accounts.

Input Schema

TableJSON 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 period: "af" (annual, default), "saf" (semi-annual), "qf" (quarterly full), "q1"/"q2"/"q3".
`symbol`	Yes	Security symbol, e.g. "AAPL.US"

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field 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."

Changed2 schema fields changedv0.10.6Sep 10, 2026

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"
-    },
-    "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": {
-    "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"
-}New value: +null

Addedv0.8.4Jul 25, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful behavioral detail: the default report period, accepted report keys, and the specific regional error code.

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?

Two compact sentences front-load the action and then pack in the essential report modes, default, and regional error behavior. There is no filler or redundant prose.

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 simple read-only tool with fully documented parameters and strong annotations, the description covers scope, report selection, defaults, and a known failure mode. It does not describe the output shape, but 'key financial metrics' provides a reasonable expectation and no output schema is available.

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 re-states the report options and default but adds no meaning beyond what the schema already provides for symbol, report, or _jq.

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 and resource: 'Get key financial metrics (fin-keyfactor) for a US symbol,' and it includes report variants and region restrictions. It is clear and actionable, though it does not explicitly differentiate itself from the similarly-named financial_report and financial_report_snapshot sibling tools.

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

Usage Guidelines4/5

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

It gives clear context on when to use: for US accounts only, and it even warns that AP accounts will trigger a DcRegionRestricted error. It does not name an alternative tool for non-US reports, so it stops short of fully routing the agent away.

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

Deploy Server

Financial Report Key Metrics (US)

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools