longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

Financial Calendar

finance_calendar

Read-onlyIdempotent

Get financial events by category—earnings, dividends, splits, IPOs, macro data, and holidays—for a date range and market to plan trades and stay informed.

Instructions

Finance calendar by category: report (earnings) / dividend / split / ipo / macrodata (CPI, NFP, rates) / closed (holidays). start and end (YYYY-MM-DD) are optional, default today plus 7 days; keep ranges under 2 weeks or results truncate.

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.
`end`	No	End date in YYYY-MM-DD format (inclusive). Defaults to 7 days after `start`.
`start`	No	Start date in YYYY-MM-DD format (inclusive). Defaults to today (UTC).
`market`	No	Optional market filter. One of: HK, US, CN, SG, JP, UK, DE, AU. Omit to include all markets.
`category`	Yes	Event category. One of: - "report": earnings reports (includes financial statements) - "dividend": dividend announcements - "split": stock splits and reverse splits (share consolidations) - "ipo": upcoming IPO listings - "macrodata": macro economic data releases (CPI, NFP, rate decisions, etc.) - "closed": market closure days

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": {
-    "FinanceCalendarBucket": {
-      "properties": {
-        "date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "infos": {
-          "items": {
-            "$ref": "#/$defs/FinanceCalendarEvent"
-          },
-          "type": [
-            "array",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "FinanceCalendarEvent": {
-      "properties": {
-        "datetime": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "market": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "symbol": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "list": {
-      "items": {
-        "$ref": "#/$defs/FinanceCalendarBucket"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    },
-    "partial": {
-      "type": [
-        "boolean",
-        "null"
-      ]
-    },
-    "partial_reason": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed5 schema fields changedv0.10.2Aug 29, 2026

changedInput schema / properties / end / description

Previous value: -"End date in YYYY-MM-DD format (inclusive)"New value: +"End date in YYYY-MM-DD format (inclusive). Defaults to 7 days after `start`."

changedInput schema / properties / start / description

Previous value: -"Start date in YYYY-MM-DD format (inclusive)"New value: +"Start date in YYYY-MM-DD format (inclusive). Defaults to today (UTC)."

changedInput schema / required

Previous value: -[
-  "category",
-  "start",
-  "end"
-]New value: +[
+  "category"
+]

addedOutput schema / properties / partial

Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}

addedOutput schema / properties / partial_reason

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

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

Changed10 schema fields changedv0.6.0Jun 26, 2026

removedOutput schema / $defs / FinanceCalendarBucket / properties / date / description
```
Removed value: -"Bucket date (yyyy-mm-dd)."
```
removedOutput schema / $defs / FinanceCalendarBucket / properties / infos / description
```
Removed value: -"Events occurring on this date."
```
removedOutput schema / $defs / FinanceCalendarEvent / properties / datetime / description
```
Removed value: -"Event time (RFC3339)."
```

removedOutput schema / $defs / FinanceCalendarEvent / properties / id / description

Removed value: -"Event ID (may be empty for events without one, e.g. market closures)."

removedOutput schema / $defs / FinanceCalendarEvent / properties / market / description
```
Removed value: -"Market code, e.g. \"US\" / \"HK\"."
```

removedOutput schema / $defs / FinanceCalendarEvent / properties / symbol / description

Removed value: -"Security symbol when the event is stock-specific, e.g. \"AAPL.US\"."

removedOutput schema / $schema

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

removedOutput schema / description

Removed value: -"Returned by `finance_calendar`. Wraps a `list` array of date buckets, each\nholding an `infos` array of events. Subset of the wire response — the\nevent field set varies by `category` (report / dividend / split / ipo /\nmacrodata / closed) and is only partially documented, so only the keys the\nmerge/dedup pipeline relies on are modeled here."

removedOutput schema / properties / list / description

Removed value: -"Date buckets, sorted ascending by date."

removedOutput schema / title

Removed value: -"FinanceCalendarResponse"

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "FinanceCalendarBucket": {
+      "properties": {
+        "date": {
+          "description": "Bucket date (yyyy-mm-dd).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "infos": {
+          "description": "Events occurring on this date.",
+          "items": {
+            "$ref": "#/$defs/FinanceCalendarEvent"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "FinanceCalendarEvent": {
+      "properties": {
+        "datetime": {
+          "description": "Event time (RFC3339).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "description": "Event ID (may be empty for events without one, e.g. market closures).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "market": {
+          "description": "Market code, e.g. \"US\" / \"HK\".",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "symbol": {
+          "description": "Security symbol when the event is stock-specific, e.g. \"AAPL.US\".",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `finance_calendar`. Wraps a `list` array of date buckets, each\nholding an `infos` array of events. Subset of the wire response — the\nevent field set varies by `category` (report / dividend / split / ipo /\nmacrodata / closed) and is only partially documented, so only the keys the\nmerge/dedup pipeline relies on are modeled here.",
+  "properties": {
+    "list": {
+      "description": "Date buckets, sorted ascending by date.",
+      "items": {
+        "$ref": "#/$defs/FinanceCalendarBucket"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "FinanceCalendarResponse",
+  "type": "object"
+}

Addedv0.4.5May 28, 2026
Removedv0.4.0May 21, 2026
Addedv0.3.2May 19, 2026
Removedv0.3.1May 15, 2026
First observedv0.1.12May 8, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already mark the tool readOnly, openWorld, idempotent, and non-destructive; the description adds useful behavioral detail beyond that by disclosing the default date range and the truncation behavior for ranges over two weeks. This goes beyond what annotations or the schema provide.

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 sentences with no filler. The category list is front-loaded, the date defaults are stated compactly, and the truncation warning earns its place as an essential constraint.

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 filtered read-only calendar with a rich schema and annotations, the description covers required category selection, optional date behavior, and the truncation constraint. It does not describe the return shape, but no output schema exists and an agent can still invoke the tool correctly with the provided information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so parameters are already well-documented, including category values, date formats, and the market filter. The description adds one extra semantic constraint not in the schema: ranges longer than two weeks truncate results, which clarifies start/end interplay.

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 identifies a specific resource (finance calendar) and enumerates its categories (report, dividend, split, ipo, macrodata, closed), which makes the tool's scope clear. It lacks an explicit verb like 'list' or 'get' and does not distinguish from sibling tools such as macrodata, dividend, or ipo_calendar, so it falls short of a 5.

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?

The description gives clear context for when to use this tool: it covers a defined set of financial event categories and states the default date window. It also adds an operational constraint (keep ranges under two weeks or results truncate), though it does not explicitly name alternatives or say when not to use it.

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

Deploy Server

Financial Calendar

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools