Skip to main content
Glama
longbridge

longbridge

Official

IPO Orders

ipo_orders
Read-onlyIdempotent

Retrieve active and historical IPO orders, filtering by symbol, market, or status to find specific orders.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ordersYes
historyYes

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: -"IpoOrdersParam"
  2. 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"
  3. 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"
      +}
  4. Addedv0.4.5
  5. Removedv0.4.0
  6. Addedv0.3.2
  7. Removedv0.3.1
  8. Addedv0.2.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint, so the description adds value by specifying it lists both active and history orders. No contradictions.

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?

Single sentence, no fluff, front-loaded with key information. 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?

Adequate for a listing tool with output schema present. Could mention pagination behavior but not critical given parameter descriptions.

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% with clear parameter descriptions. The description summarizes filtering options but does not add new meaning beyond the schema.

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?

Clearly states it lists IPO orders (active and history) and mentions filtering by symbol, market, or status. Distinguished from sibling tools like ipo_detail or ipo_order_detail.

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?

Implies usage through description but does not explicitly state when to use this tool versus alternatives like ipo_order_detail or ipo_calendar. No exclusion conditions.

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