Skip to main content
Glama
longbridge

longbridge

Official

IPO Detail

ipo_detail
Read-onlyIdempotent

Retrieve comprehensive IPO details for any symbol: company profile, offering timeline, subscription eligibility, pricing range, lot size, and allotment rules.

Instructions

Show IPO detail for a symbol. Returns profile (business overview), timeline[]{event, date}, subscription eligibility, pricing_range, lot_size, allotment_rules.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesSecurity symbol, e.g. "6871.HK" or "ARM.US"
marketNoMarket: "HK" or "US" (default: inferred from symbol suffix)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNoBusiness overview / profile payload (passthrough, shape upstream-defined).
timelineNoTimeline events. The upstream payload may wrap this differently; the documented portion is a list of `{event, date}` entries.
eligibilityNoSubscription eligibility payload (passthrough, shape upstream-defined).
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds the return structure (e.g., timeline array) but no additional behavioral context like auth needs or rate limits. 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, front-loaded sentence that efficiently states purpose and return fields. No redundancy.

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

Completeness5/5

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

Given the output schema exists, the description sufficiently summarizes return values. Annotations and schema cover behavioral and parameter needs. Complete for an AI agent.

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%; the description does not add meaning beyond the schema beyond implying the 'symbol' parameter is used. No new parameter details.

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?

The description clearly states the tool returns IPO details for a symbol, listing specific fields (profile, timeline, etc.), distinguishing it from siblings like ipo_calendar or 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for fetching comprehensive IPO data for a specific symbol, but lacks explicit when-to-use vs alternatives like ipo_calendar (list) or ipo_subscriptions (subscription details).

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