longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

IPO Calendar

ipo_calendar

Read-onlyIdempotent

Retrieve upcoming IPO dates, symbols, and listing details for US and HK markets to plan investment research around new stock debuts.

Instructions

Show the IPO calendar.

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.

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": {
-    "IpoItem": {
-      "properties": {
-        "issue_price": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "listing_date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "market": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "min_lot_size": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "name": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "status": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "sub_end_date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "sub_start_date": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "symbol": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "items": {
-      "items": {
-        "$ref": "#/$defs/IpoItem"
-      },
-      "type": [
-        "array",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

Changed14 schema fields changedv0.6.0Jun 26, 2026

removedOutput schema / $defs / IpoItem / description

Removed value: -"A single IPO entry as it appears in the subscription / calendar / listed\nfeeds. Subset of the upstream item; field availability varies by feed and\nmarket. Numeric/price fields are stringified by the transform pipeline."

removedOutput schema / $defs / IpoItem / properties / issue_price / description
```
Removed value: -"Issue price (stringified decimal)."
```
removedOutput schema / $defs / IpoItem / properties / listing_date / description
```
Removed value: -"Listing date (yyyy-mm-dd)."
```
removedOutput schema / $defs / IpoItem / properties / market / description
```
Removed value: -"Market code, e.g. \"HK\" / \"US\"."
```
removedOutput schema / $defs / IpoItem / properties / min_lot_size / description
```
Removed value: -"Minimum lot size for subscription."
```
removedOutput schema / $defs / IpoItem / properties / name / description
```
Removed value: -"Display name of the security."
```
removedOutput schema / $defs / IpoItem / properties / status / description
```
Removed value: -"IPO status (calendar feed), e.g. upcoming / listed."
```
removedOutput schema / $defs / IpoItem / properties / sub_end_date / description
```
Removed value: -"Subscription window end date (yyyy-mm-dd)."
```
removedOutput schema / $defs / IpoItem / properties / sub_start_date / description
```
Removed value: -"Subscription window start date (yyyy-mm-dd)."
```
removedOutput schema / $defs / IpoItem / properties / symbol / description
```
Removed value: -"Security symbol, e.g. \"6871.HK\" or \"ARM.US\"."
```

removedOutput schema / $schema

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

removedOutput schema / description

Removed value: -"Returned by `ipo_calendar`. Passthrough of the upstream calendar payload;\nthe documented portion is `items[]`. The upstream `timestamp` is converted\nto RFC3339 by the unix-path transform."

removedOutput schema / properties / items / description

Removed value: -"Calendar entries for upcoming and recent IPOs."

removedOutput schema / title
```
Removed value: -"IpoCalendarResponse"
```

Changed1 schema field changedv0.5.6Jun 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "IpoItem": {
+      "description": "A single IPO entry as it appears in the subscription / calendar / listed\nfeeds. Subset of the upstream item; field availability varies by feed and\nmarket. Numeric/price fields are stringified by the transform pipeline.",
+      "properties": {
+        "issue_price": {
+          "description": "Issue price (stringified decimal).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "listing_date": {
+          "description": "Listing date (yyyy-mm-dd).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "market": {
+          "description": "Market code, e.g. \"HK\" / \"US\".",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "min_lot_size": {
+          "description": "Minimum lot size for subscription.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "name": {
+          "description": "Display name of the security.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "status": {
+          "description": "IPO status (calendar feed), e.g. upcoming / listed.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "sub_end_date": {
+          "description": "Subscription window end date (yyyy-mm-dd).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "sub_start_date": {
+          "description": "Subscription window start date (yyyy-mm-dd).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "symbol": {
+          "description": "Security symbol, e.g. \"6871.HK\" or \"ARM.US\".",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `ipo_calendar`. Passthrough of the upstream calendar payload;\nthe documented portion is `items[]`. The upstream `timestamp` is converted\nto RFC3339 by the unix-path transform.",
+  "properties": {
+    "items": {
+      "description": "Calendar entries for upcoming and recent IPOs.",
+      "items": {
+        "$ref": "#/$defs/IpoItem"
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    }
+  },
+  "title": "IpoCalendarResponse",
+  "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.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description adds no behavioral context beyond the verb 'Show'. It does not describe what data is returned or any limitations. It merely repeats the read-only nature already declared.

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 extremely brief with no fluff, which is good for conciseness. However, it is so minimal it borders on under-specification rather than effective conciseness.

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

Completeness2/5

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

The tool has no output schema and the description gives no indication of what the IPO calendar contains, what time range it covers, or how it differs from related tools like ipo_listed. This is inadequate for an agent to call it correctly.

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?

The only parameter _jq is fully documented in the schema (100% coverage). The description does not need to add parameter details, so a baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Show the IPO calendar' simply restates the tool name and title. It does not distinguish this from the many other IPO-related sibling tools (ipo_listed, ipo_detail, ipo_subscriptions) and lacks specificity about what the calendar contains.

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?

No guidance is given on when to use this tool versus alternatives. An agent has no way to know if this is the right tool for upcoming IPOs, historical IPOs, or a specific date range.

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

Deploy Server

IPO Calendar

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools