Skip to main content
Glama
longbridge

longbridge

Official

IPO Order Detail

ipo_order_detail
Read-onlyIdempotent

Retrieve detailed information for a specific IPO order, including order ID, symbol, market, quantity, allotted amount, total amount, status, and submission time.

Instructions

Show detailed information for a specific IPO order by order_id. Returns {order_id, symbol, market, quantity, allotted_quantity, total_amount, status, submitted_at}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idYesIPO order ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
order_idNoIPO order ID.
symbolNoSecurity symbol, e.g. "6871.HK".
marketNoMarket code, e.g. "HK" / "US".
quantityNoSubscription quantity.
allotted_quantityNoAllotted quantity after the IPO drawing.
total_amountNoTotal subscription amount (stringified decimal).
statusNoOrder status.
submitted_atNoOrder submission time (RFC3339).
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds detail on the return fields, which provides clarity on the tool's behavior beyond the annotations. However, no additional traits (e.g., authorization, rate limits) are mentioned.

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?

One sentence plus a list of return fields. Extremely concise, front-loaded, and every element is necessary.

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?

Given the simple nature (1 param, no nested objects, output schema exists), the description is complete. It covers purpose, parameter, and return fields. Minor improvement could be error conditions, but not needed for basic completeness.

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 provides 100% coverage for 'order_id' with description 'IPO order ID'. The description mentions 'by order_id' but adds no extra semantic meaning. Baseline is 3 since schema is sufficient.

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?

Description clearly states the verb 'Show', the resource 'IPO order', and the key parameter 'order_id'. It distinguishes from sibling tools like 'ipo_orders' (list) and 'order_detail' (regular orders) by specifying 'IPO order' and listing specific return fields.

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?

Description does not explicitly state when to use this tool vs alternatives like 'ipo_orders' or 'order_detail'. Usage is implied but not guided, and no when-not scenarios are provided.

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