Skip to main content
Glama
longbridge

longbridge

Official

IPO Subscriptions

ipo_subscriptions
Read-onlyIdempotent

Identify IPO stocks currently in subscription or pre-filing stage across Hong Kong and US markets.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hkYes
usYes

Schema Changelog

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

  1. Changed17 schema fields changedv0.6.0
    • 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"
  2. Changed1 schema field changedv0.5.6
    • 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"
      +}
  3. Addedv0.4.5
  4. Removedv0.4.0
  5. Addedv0.3.2
  6. Removedv0.3.1
  7. 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, destructiveHint. Description adds market scope and stage, but does not disclose any additional behavioral traits like pagination or output limits.

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, front-loaded with the verb 'List', no unnecessary words. Efficient and to the point.

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?

Low complexity tool with no parameters and presence of output schema. Description covers purpose and scope but could mention output format or return details for completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has zero parameters, so schema coverage is 100%. No parameters to explain, so baseline 4 is appropriate. Description does not need to add parameter info.

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 verb 'List', resource 'IPO stocks', and specifies stage ('subscription/pre-filing') and markets ('HK+US'). Distinguishes from sibling tools like ipo_calendar, ipo_detail, ipo_listed.

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 explicit guidance on when to use this tool over alternatives. Does not mention exclusions or provide context for selection among sibling IPO tools.

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