Skip to main content
Glama
longbridge

longbridge

Official
by longbridge
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Rust
Hybrid

IPO Detail

ipo_detail
Read-onlyIdempotent

Retrieve detailed IPO information for a specific US or HK stock symbol, including dates, prices, and offering details, to evaluate new listings.

Instructions

Show IPO detail for a symbol.

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.
marketNoMarket: "HK" or "US" (default: inferred from symbol suffix)
symbolYesSecurity symbol, e.g. "6871.HK" or "ARM.US"

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": {
-    "eligibility": {},
-    "profile": {},
-    "timeline": {}
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"IpoDetailParam"
  4. Changed6 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_detail`. The tool combines three upstream payloads\n(`profile`, `timeline`, `eligibility`) under one wrapper object. Each part\nis a passthrough; only the documented portions are typed here."
    • removedOutput schema / properties / eligibility / description
      Removed value: -"Subscription eligibility payload (passthrough, shape upstream-defined)."
    • removedOutput schema / properties / profile / description
      Removed value: -"Business overview / profile payload (passthrough, shape upstream-defined)."
    • removedOutput schema / properties / timeline / description
      Removed value: -"Timeline events. The upstream payload may wrap this differently; the\ndocumented portion is a list of `{event, date}` entries."
    • removedOutput schema / title
      Removed value: -"IpoDetailResponse"
  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_detail`. The tool combines three upstream payloads\n(`profile`, `timeline`, `eligibility`) under one wrapper object. Each part\nis a passthrough; only the documented portions are typed here.",
+  "properties": {
+    "eligibility": {
+      "description": "Subscription eligibility payload (passthrough, shape upstream-defined)."
+    },
+    "profile": {
+      "description": "Business overview / profile payload (passthrough, shape upstream-defined)."
+    },
+    "timeline": {
+      "description": "Timeline events. The upstream payload may wrap this differently; the\ndocumented portion is a list of `{event, date}` entries."
+    }
+  },
+  "title": "IpoDetailResponse",
+  "type": "object"
+}
  6. Addedv0.4.5
  7. Removedv0.4.0
  8. Addedv0.3.2
  9. Removedv0.3.1
  10. Addedv0.2.1

TDQS

B3.3/5.0
Behavior2/5

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

The description adds no behavioral information beyond the annotations: readOnlyHint, idempotentHint, and destructiveHint=false already establish safety. It does not disclose what 'detail' includes, the response shape, or any formatting/pagination behavior, so it provides little transparency beyond structured metadata.

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, front-loaded sentence with no filler. It is appropriately concise for a tool whose parameters and safety profile are already covered by the schema and annotations.

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?

The tool is simple (one required parameter, full schema documentation) and annotations establish its read-only, idempotent nature, so an agent can invoke it from the schema alone. However, with no output schema and many IPO-related sibling tools, the description could be richer to aid confident tool selection and set expectations for the response.

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 description coverage is 100%, so all three parameters (symbol, market, _jq) are fully documented in the schema. The description's mention of 'a symbol' merely echoes the existing parameter documentation and adds no new meaning about market inference or jq filtering.

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 IPO detail for a symbol' provides a clear verb ('Show'), a resource ('IPO detail'), and a scope ('for a symbol'), so the core purpose is unambiguous. It does not differentiate this tool from the many ipo_* sibling tools like ipo_listed or ipo_calendar, which is the main clarity gap.

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 phrase 'for a symbol' implies this is the single-symbol IPO detail lookup, giving some situational context. However, there is no explicit mention of when to use this tool instead of alternatives such as ipo_listed or ipo_calendar, nor any exclusions.

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