longbridge

Official

by longbridge

Overview Schema Source Related Servers Discussions(1)Admin

Rust

Hybrid

IPO Subscriptions

ipo_subscriptions

Read-onlyIdempotent

Get IPO stocks in subscription or pre-filing stage for Hong Kong and US markets to monitor upcoming offerings.

Instructions

List IPO stocks in subscription/pre-filing stage (HK+US).

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"
-    },
-    "IpoMarketFeed": {
-      "properties": {
-        "items": {
-          "items": {
-            "$ref": "#/$defs/IpoItem"
-          },
-          "type": [
-            "array",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "hk": {
-      "$ref": "#/$defs/IpoMarketFeed"
-    },
-    "us": {
-      "$ref": "#/$defs/IpoMarketFeed"
-    }
-  },
-  "required": [
-    "hk",
-    "us"
-  ],
-  "type": "object"
-}New value: +null

Changed17 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 / $defs / IpoMarketFeed / description

Removed value: -"One side (HK or US) of an IPO feed that splits results by market. Each side\nis the raw upstream payload; the documented portion is `items[]`."

removedOutput schema / $defs / IpoMarketFeed / properties / items / description

Removed value: -"IPO entries for this market (documented subset of upstream fields)."

removedOutput schema / $schema

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

removedOutput schema / description

Removed value: -"Returned by `ipo_subscriptions`. HK and US subscription feeds combined under\na `{hk, us}` wrapper object built by the tool."

removedOutput schema / properties / hk / description

Removed value: -"Hong Kong subscription / pre-filing feed."

removedOutput schema / properties / us / description

Removed value: -"US subscription / pre-filing feed."

removedOutput schema / title

Removed value: -"IpoSubscriptionsResponse"

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"
+    },
+    "IpoMarketFeed": {
+      "description": "One side (HK or US) of an IPO feed that splits results by market. Each side\nis the raw upstream payload; the documented portion is `items[]`.",
+      "properties": {
+        "items": {
+          "description": "IPO entries for this market (documented subset of upstream fields).",
+          "items": {
+            "$ref": "#/$defs/IpoItem"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `ipo_subscriptions`. HK and US subscription feeds combined under\na `{hk, us}` wrapper object built by the tool.",
+  "properties": {
+    "hk": {
+      "$ref": "#/$defs/IpoMarketFeed",
+      "description": "Hong Kong subscription / pre-filing feed."
+    },
+    "us": {
+      "$ref": "#/$defs/IpoMarketFeed",
+      "description": "US subscription / pre-filing feed."
+    }
+  },
+  "required": [
+    "hk",
+    "us"
+  ],
+  "title": "IpoSubscriptionsResponse",
+  "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

A4/5.0

Behavior3/5

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds scoping behavior (which stages and markets are included) but does not disclose output shape, pagination, or data freshness. This is adequate but not rich behavioral context.

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 a single front-loaded sentence with no filler. Every element—action, resource, stage, market—contributes directly to tool selection and invocation.

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 zero-required-parameter read-only list tool, the description is nearly complete. It states exactly what is listed and in which markets. Since there is no output schema, a brief note on the response shape would improve completeness, but it is not essential for correct invocation.

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 with detailed semantics and an example. The description does not need to repeat this, so the baseline score of 3 is appropriate.

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

Purpose5/5

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

The description uses a specific verb, 'List', with a clear resource: IPO stocks in subscription/pre-filing stage, scoped to HK+US. This uniquely distinguishes the tool from siblings like ipo_listed, ipo_calendar, and ipo_detail. An agent can identify when this tool applies without opening schemas.

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: use this for IPOs that are in subscription or pre-filing stage, not yet listed. It does not explicitly name alternatives or state when-not-to-use cases, but the stage and market scoping effectively communicates the intended use.

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

Deploy Server

IPO Subscriptions

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools