ipo_detailGet IPO details for a stock symbol in US or HK markets, with market auto-detected from the symbol suffix.
Show IPO detail for a symbol.
| Name | Required | Description | Default |
|---|---|---|---|
| market | No | Market: "HK" or "US" (default: inferred from symbol suffix) | |
| symbol | Yes | Security symbol, e.g. "6871.HK" or "ARM.US" |
| Name | Required | Description | Default |
|---|---|---|---|
| profile | No | ||
| timeline | No | ||
| eligibility | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.7.1Input schema / titleRemoved value: -"IpoDetailParam"v0.6.0Output schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Output schema / descriptionRemoved 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."Output schema / properties / eligibility / descriptionRemoved value: -"Subscription eligibility payload (passthrough, shape upstream-defined)."Output schema / properties / profile / descriptionRemoved value: -"Business overview / profile payload (passthrough, shape upstream-defined)."Output schema / properties / timeline / descriptionRemoved value: -"Timeline events. The upstream payload may wrap this differently; the\ndocumented portion is a list of `{event, date}` entries."Output schema / titleRemoved value: -"IpoDetailResponse"v0.5.6Output 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"
+}v0.4.5v0.4.0v0.3.2v0.3.1v0.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description only says 'Show' and adds no additional behavioral context such as data freshness, possible delays, or reliance on market data. Minimal value beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no wasted words. It is appropriately front-loaded and concise for a simple read operation.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having an output schema and annotations, the description is too terse for a tool in a large family of IPO-related siblings. It does not indicate what constitutes 'detail' (e.g., pricing, dates, shares) or contrast with similar tools, leaving the agent unsure of its precise scope.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description does not add meaning beyond the schema; it merely restates that the tool shows detail 'for a symbol', which is already captured in the parameter descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Show' and the resource 'IPO detail for a symbol'. However, it does not differentiate from sibling tools like 'ipo_calendar' or 'ipo_listed', which are also IPO-related. The name 'ipo_detail' suggests a detailed view, but this is not explicitly confirmed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 such as 'ipo_calendar' for listing or 'ipo_subscriptions' for subscription data. The description lacks context about prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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