Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersScoreDiscussions(1)Admin
Rust
Hybrid

IPO Order Detail

ipo_order_detail
Read-onlyIdempotent

Retrieve comprehensive details for a specific IPO order by order ID, including status and allocation, to track your subscription.

Instructions

Show detailed information for a specific IPO order by order_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYesIPO order ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketNo
statusNo
symbolNo
order_idNo
quantityNo
submitted_atNo
total_amountNo
allotted_quantityNo

Schema Changelog

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

  1. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"IpoOrderDetailParam"
  2. 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"
  3. 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"
+}
  4. Addedv0.4.5
  5. Removedv0.4.0
  6. Addedv0.3.2
  7. Removedv0.3.1
  8. 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 declare readOnlyHint, openWorldHint, idempotentHint, and not destructive. The description adds no extra behavioral context (e.g., no mention of authentication, rate limits, or output structure). It does not contradict 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?

The description is a single sentence of 13 words, immediately conveying the tool's purpose and primary input. Every word is essential, with no fluff or redundancy.

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 retrieval tool with one parameter, annotations covering safety, and an existing output schema, the description is sufficiently complete. It could optionally note that the order_id must come from ipo_orders, but this is not required for correct usage.

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 coverage is 100% and the description of 'order_id' as 'IPO order ID' mirrors the schema property description. No additional meaning, format, or examples are provided beyond what the schema already gives. Baseline 3 applies.

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 clearly states the action ('Show detailed information'), the resource ('a specific IPO order'), and the identifier ('by order_id'). It distinguishes from sibling tools like ipo_orders (which lists orders) and order_detail (for regular orders) through the specific mention of IPO orders.

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 implies usage when you have an order_id for an IPO order, but lacks explicit guidance on when to use this tool over alternatives (e.g., ipo_orders for listing, order_detail for non-IPO orders). No when-not-to-use or prerequisites are stated.

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