Skip to main content
Glama
hk-ipo-fee-mcp

hk-ipo-fee-mcp

hk_ipo_plan

Calculates Hong Kong IPO subscription costs, margin interest, break-even sell price, and scenario P&L or expected value from your offer price, lot size, and fee inputs.

Instructions

Full HK IPO subscription plan: entry fee, total payable, own cash vs margin loan, margin interest (loan × rate × days / 365), fixed cost, break-even sell price (after 0.1% stamp duty rounded up to HK$1, trading fee, levies, broker charges) and P&L / expected value under day-one change scenarios. annual_rate and sell_commission_rate are fractions (0.035 = 3.5%). allot_probability is 0..1, or pass valid_applications + successful_applicants from the allotment results announcement.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "offer_price": "<offer_price>",
      "board_lot": "<board_lot>"
    },
    "name": "hk_ipo_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
board_lotYes
annual_rateNo
offer_priceYes
handling_feeNo
lots_appliedNo
allotted_lotsNo
financing_feeNo
interest_daysNo
scenarios_pctNo
margin_multipleNo
allot_probabilityNo
sell_platform_feeNo
valid_applicationsNo
sell_min_commissionNo
sell_commission_rateNo
successful_applicantsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well by disclosing the calculation model: margin interest as loan × rate × days / 365, break-even pricing with stamp duty rounding, and P&L under day-one scenarios. It does not discuss error behavior or assumptions, but the core computational behavior is unusually transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the tool's purpose and then packs useful formulas and unit clarifications into a compact paragraph. It is dense but not wasteful, and every clause contributes to understanding the calculation.

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?

For a complex 16-parameter financial calculator with no annotations and no output schema, the description covers the main outputs and key calculation rules. However, it leaves many optional parameters and output structure details unspecified, so it is adequate but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 16 parameters, so the description must compensate. It clarifies important semantics for annual_rate, sell_commission_rate, allot_probability, valid_applications, and successful_applicants, but many inputs such as handling_fee, financing_fee, scenarios_pct, sell_platform_fee, and sell_min_commission remain undocumented beyond their titles.

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 states a specific resource and scope: a full HK IPO subscription plan covering entry fee, payable amount, margin loan, break-even sell price, and scenario P&L. It is clear what the tool computes, but it does not explicitly distinguish itself from siblings such as hk_ipo_amount_payable or hk_sell_costs.

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?

The description does not say when to use this tool versus hk_ipo_amount_payable, hk_sell_costs, or other siblings. It gives an alternative input method for allotment probability, but that is parameter guidance rather than tool-selection guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.