Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersScoreDiscussions(1)Admin
Rust
Hybrid

Financial Calendar

finance_calendar
Read-onlyIdempotent

Retrieve financial events by category—earnings, dividends, splits, IPOs, macro data, or market closures—with optional date range and market filter.

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
NameRequiredDescriptionDefault
endNoEnd date in YYYY-MM-DD format (inclusive). Defaults to 7 days after `start`.
startNoStart date in YYYY-MM-DD format (inclusive). Defaults to today (UTC).
marketNoOptional market filter. One of: HK, US, CN, SG, JP, UK, DE, AU. Omit to include all markets.
categoryYesEvent 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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
listNo
partialNo
partial_reasonNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv0.10.2
    • 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"
+  ]
+}
  2. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"FinanceCalendarParam"
  3. Changed10 schema fields changedv0.6.0
    • 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"
  4. Changed1 schema field changedv0.5.6
    • 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"
+}
  5. Addedv0.4.5
  6. Removedv0.4.0
  7. Addedv0.3.2
  8. Removedv0.3.1
  9. First observedv0.1.12

TDQS

A4/5.0
Behavior5/5

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

Annotations already establish readOnly, idempotent, openWorld, and non-destructive behavior. The description adds meaningful behavioral context beyond annotations: start/end default to today plus 7 days, and ranges over 2 weeks cause results to truncate. It also clarifies category scope (e.g., macrodata includes CPI, NFP, rates). No contradiction with 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?

Two compact sentences: the first front-loads the category list, the second conveys default dates and the range limit. Every phrase earns its place, with no redundant or filler content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists and annotations cover the safety profile. The description gives everything needed to call the tool correctly: required category, optional start/end with defaults and range limit. The only gap, guidance on when to use this over sibling tools, was already penalized under usage_guidelines.

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 the baseline is 3. The description enriches the start/end parameters by stating defaults and the truncation policy, which the schema does not include. Category examples in the description mirror the schema but add useful concrete instances (CPI, NFP, rates).

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 the resource (finance calendar) and enumerates specific event categories with examples (report, dividend, split, ipo, macrodata, closed). It is not verb-driven like 'List...' but clearly conveys that this is a calendar of financial events by category. It distinguishes from dedicated siblings by spanning multiple categories, though it doesn't explicitly contrast them.

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?

The description provides no guidance on when to use finance_calendar versus dedicated sibling tools such as ipo_calendar, macrodata, dividend, trading_days, or corp_action. The only usage notes are about default date ranges and truncation, which relate to parameters, not tool selection. No alternatives or exclusions are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/longbridge/longbridge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server