Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

IPO Order Detail

ipo_order_detail
Read-onlyIdempotent

Retrieve detailed information for a specific IPO order by providing its order ID, including status, pricing, and allocation details.

Instructions

Show detailed information for a specific IPO order by order_id.

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.
order_idYesIPO order ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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."
  2. Changed2 schema fields changedv0.10.6
    • addedInput schema / properties / _jq
      Added value: +{
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "allotted_quantity": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "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"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"IpoOrderDetailParam"
  4. Changed11 schema fields changedv0.6.0
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `ipo_order_detail`. Passthrough of a single IPO order; the\ndocumented subset is typed here. Amount fields are stringified decimals and\n`submitted_at` is RFC3339."
    • removedOutput schema / properties / allotted_quantity / description
      Removed value: -"Allotted quantity after the IPO drawing."
    • removedOutput schema / properties / market / description
      Removed value: -"Market code, e.g. \"HK\" / \"US\"."
    • removedOutput schema / properties / order_id / description
      Removed value: -"IPO order ID."
    • removedOutput schema / properties / quantity / description
      Removed value: -"Subscription quantity."
    • removedOutput schema / properties / status / description
      Removed value: -"Order status."
    • removedOutput schema / properties / submitted_at / description
      Removed value: -"Order submission time (RFC3339)."
    • removedOutput schema / properties / symbol / description
      Removed value: -"Security symbol, e.g. \"6871.HK\"."
    • removedOutput schema / properties / total_amount / description
      Removed value: -"Total subscription amount (stringified decimal)."
    • removedOutput schema / title
      Removed value: -"IpoOrderDetailResponse"
  5. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Returned by `ipo_order_detail`. Passthrough of a single IPO order; the\ndocumented subset is typed here. Amount fields are stringified decimals and\n`submitted_at` is RFC3339.",
+  "properties": {
+    "allotted_quantity": {
+      "description": "Allotted quantity after the IPO drawing.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "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"
+      ]
+    }
+  },
+  "title": "IpoOrderDetailResponse",
+  "type": "object"
+}
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. Addedv0.2.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds no additional behavioral details such as response format or pagination. It is neutral and does not contradict annotations, so a baseline 3 is appropriate.

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 with no filler. It front-loads the action and resource. This is an optimal level of conciseness.

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 simple read-only tool with one required parameter, the description is sufficient. It tells the agent exactly what the tool does. Given the annotations cover safety, no further context is needed. However, it does not describe the structure of the returned detail, but since no output schema exists, that is not strictly required.

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?

Both parameters are fully described in the schema (order_id and _jq), with 100% coverage. The description adds no extra semantics beyond what the schema provides, so it earns the baseline 3.

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 clearly states a verb (Show) and a specific resource (IPO order) identified by order_id. It is distinguishable from sibling tools like ipo_orders (which likely lists) and order_detail (non-IPO) based on the resource type. However, it does not explicitly name alternatives, so slightly less than a perfect 5.

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 provided on when to use this tool versus alternatives such as ipo_orders or order_detail. The description only states the action without any context about selection criteria.

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