Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

IPO Orders

ipo_orders
Read-onlyIdempotent

List active and historical IPO orders with filters for symbol, market, or status to track subscriptions.

Instructions

List IPO orders (active+history). Filter by symbol, market, or status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_jqNoOptional 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.
pageNoPage number (default: 1)
sizeNoPage size (default: 20)
marketNoFilter by market: "HK" or "US"
statusNoFilter by order status
symbolNoFilter by symbol, e.g. "6871.HK"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.12.0
    • 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."
    • removedInput schema / properties / page / format
      Removed value: -"uint32"
    • removedInput schema / properties / size / format
      Removed value: -"uint32"
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "$defs": {
-    "IpoOrderItem": {
-      "properties": {
-        "market": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "order_id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "quantity": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "status": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "submitted_at": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "symbol": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "total_amount": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    },
-    "IpoOrdersFeed": {
-      "properties": {
-        "orders": {
-          "items": {
-            "$ref": "#/$defs/IpoOrderItem"
-          },
-          "type": [
-            "array",
-            "null"
-          ]
-        }
-      },
-      "type": "object"
-    }
-  },
-  "properties": {
-    "history": {
-      "$ref": "#/$defs/IpoOrdersFeed"
-    },
-    "orders": {
-      "$ref": "#/$defs/IpoOrdersFeed"
-    }
-  },
-  "required": [
-    "orders",
-    "history"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"IpoOrdersParam"
  4. Changed15 schema fields changedv0.6.0
    • removedOutput schema / $defs / IpoOrderItem / description
      Removed value: -"A single IPO order entry. Subset of upstream fields; amount fields are\nstringified by the transform pipeline and `submitted_at` is RFC3339."
    • removedOutput schema / $defs / IpoOrderItem / properties / market / description
      Removed value: -"Market code, e.g. \"HK\" / \"US\"."
    • removedOutput schema / $defs / IpoOrderItem / properties / order_id / description
      Removed value: -"IPO order ID."
    • removedOutput schema / $defs / IpoOrderItem / properties / quantity / description
      Removed value: -"Subscription quantity."
    • removedOutput schema / $defs / IpoOrderItem / properties / status / description
      Removed value: -"Order status."
    • removedOutput schema / $defs / IpoOrderItem / properties / submitted_at / description
      Removed value: -"Order submission time (RFC3339)."
    • removedOutput schema / $defs / IpoOrderItem / properties / symbol / description
      Removed value: -"Security symbol, e.g. \"6871.HK\"."
    • removedOutput schema / $defs / IpoOrderItem / properties / total_amount / description
      Removed value: -"Total subscription amount (stringified decimal)."
    • removedOutput schema / $defs / IpoOrdersFeed / description
      Removed value: -"One side of the IPO orders feed (active or historical). The documented\nportion is `orders[]`."
    • removedOutput schema / $defs / IpoOrdersFeed / properties / orders / description
      Removed value: -"IPO order entries (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_orders`. Active orders and order history combined under an\n`{orders, history}` wrapper object built by the tool."
    • removedOutput schema / properties / history / description
      Removed value: -"Historical IPO orders feed."
    • removedOutput schema / properties / orders / description
      Removed value: -"Active IPO orders feed."
    • removedOutput schema / title
      Removed value: -"IpoOrdersResponse"
  5. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "IpoOrderItem": {
+      "description": "A single IPO order entry. Subset of upstream fields; amount fields are\nstringified by the transform pipeline and `submitted_at` is RFC3339.",
+      "properties": {
+        "market": {
+          "description": "Market code, e.g. \"HK\" / \"US\".",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "order_id": {
+          "description": "IPO order ID.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "quantity": {
+          "description": "Subscription quantity.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "status": {
+          "description": "Order status.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "submitted_at": {
+          "description": "Order submission time (RFC3339).",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "symbol": {
+          "description": "Security symbol, e.g. \"6871.HK\".",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "total_amount": {
+          "description": "Total subscription amount (stringified decimal).",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "IpoOrdersFeed": {
+      "description": "One side of the IPO orders feed (active or historical). The documented\nportion is `orders[]`.",
+      "properties": {
+        "orders": {
+          "description": "IPO order entries (documented subset of upstream fields).",
+          "items": {
+            "$ref": "#/$defs/IpoOrderItem"
+          },
+          "type": [
+            "array",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `ipo_orders`. Active orders and order history combined under an\n`{orders, history}` wrapper object built by the tool.",
+  "properties": {
+    "history": {
+      "$ref": "#/$defs/IpoOrdersFeed",
+      "description": "Historical IPO orders feed."
+    },
+    "orders": {
+      "$ref": "#/$defs/IpoOrdersFeed",
+      "description": "Active IPO orders feed."
+    }
+  },
+  "required": [
+    "orders",
+    "history"
+  ],
+  "title": "IpoOrdersResponse",
+  "type": "object"
+}
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. Addedv0.2.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already carry readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds the scope 'active+history' and the available filter dimensions, which is useful but does not go into return format or any edge cases.

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 sentence that front-loads the purpose and then the filters. No filler or redundancy; every word earns its place.

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 read-only list tool with six optional parameters and no output schema, the description captures the essential purpose and scope. Minor gaps are the lack of explicit mention of where to get single-order details or what the response array contains, but the name and verb 'List' make it inferable.

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 each parameter is already documented. The description's mention of symbol, market, and status mirrors the schema and adds no new semantic value, so baseline 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?

Description states a specific verb and resource ('List IPO orders') and clarifies that both active and history are included. This distinguishes it from detail-oriented siblings like ipo_order_detail and calendar tools.

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

Usage Guidelines3/5

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

The description gives implied usage by stating it lists IPO orders and supports filtering, but it never names alternatives or exclusions. Siblings like ipo_order_detail and ipo_subscriptions exist, and the agent is not told when to choose one over the other.

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

Deploy Server

Other Tools