Skip to main content
Glama
longbridge

longbridge

Official

IPO Calendar

ipo_calendar
Read-onlyIdempotent

View upcoming initial public offerings for US and Hong Kong markets. Check the IPO calendar to track new listings and plan your investment strategy.

Instructions

Show the IPO calendar.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNo

Schema Changelog

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

  1. Changed14 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 / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `ipo_calendar`. Passthrough of the upstream calendar payload;\nthe documented portion is `items[]`. The upstream `timestamp` is converted\nto RFC3339 by the unix-path transform."
    • removedOutput schema / properties / items / description
      Removed value: -"Calendar entries for upcoming and recent IPOs."
    • removedOutput schema / title
      Removed value: -"IpoCalendarResponse"
  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"
      +    }
      +  },
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "description": "Returned by `ipo_calendar`. Passthrough of the upstream calendar payload;\nthe documented portion is `items[]`. The upstream `timestamp` is converted\nto RFC3339 by the unix-path transform.",
      +  "properties": {
      +    "items": {
      +      "description": "Calendar entries for upcoming and recent IPOs.",
      +      "items": {
      +        "$ref": "#/$defs/IpoItem"
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    }
      +  },
      +  "title": "IpoCalendarResponse",
      +  "type": "object"
      +}
  3. Addedv0.4.5
  4. Removedv0.4.0
  5. Addedv0.3.2
  6. Removedv0.3.1
  7. 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, openWorldHint, idempotentHint, and destructiveHint, covering safety. The description adds no extra behavioral context (e.g., what the calendar specifically shows). 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 concise sentence with no unnecessary words. It front-loads the purpose clearly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema, the description does not need to explain return values. However, it lacks details on the calendar's scope (e.g., dates, events), making it minimally complete for a tool in a complex domain.

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?

There are zero parameters, so the input schema is fully covered (100% schema description coverage). The description adds no param info, but none is needed. Baseline 4 is appropriate.

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 'Show the IPO calendar' clearly states the verb (show) and resource (IPO calendar). However, it does not differentiate from sibling IPO tools like ipo_detail, ipo_listed, etc., which could be confused with this tool.

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. The description does not mention any prerequisites or context where this tool is preferred.

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