Skip to main content
Glama
longbridge

longbridge

Official

IPO Profit / Loss

ipo_profit_loss
Read-onlyIdempotent

Shows IPO profit/loss summary and per-stock breakdown, filterable by all, YTD, 1-year, or 3-year periods.

Instructions

Show IPO profit/loss summary and per-stock breakdown. period: all/ytd/1y/3y.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default: 1)
sizeNoPage size (default: 20)
periodNoPeriod filter: "all", "ytd", "1y", "3y" (default: "all")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
summaryYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.7.1
    • removedInput schema / title
      Removed value: -"IpoProfitLossParam"
  2. Changed16 schema fields changedv0.6.0
    • removedOutput schema / $defs / IpoProfitLossItem / description
      Removed value: -"A single per-stock IPO profit/loss breakdown item. Subset of upstream\nfields; monetary and rate fields are stringified by the transform pipeline."
    • removedOutput schema / $defs / IpoProfitLossItem / properties / cost / description
      Removed value: -"Cost basis for this stock (stringified decimal)."
    • removedOutput schema / $defs / IpoProfitLossItem / properties / current_value / description
      Removed value: -"Current market value for this stock (stringified decimal)."
    • removedOutput schema / $defs / IpoProfitLossItem / properties / return_rate / description
      Removed value: -"Return rate for this stock (stringified decimal / percentage)."
    • removedOutput schema / $defs / IpoProfitLossItem / properties / symbol / description
      Removed value: -"Security symbol, e.g. \"6871.HK\"."
    • removedOutput schema / $defs / IpoProfitLossItems / description
      Removed value: -"The items side of the IPO profit/loss feed. The documented portion is\n`items[]`."
    • removedOutput schema / $defs / IpoProfitLossItems / properties / items / description
      Removed value: -"Per-stock profit/loss breakdown entries."
    • removedOutput schema / $defs / IpoProfitLossSummary / description
      Removed value: -"The summary side of the IPO profit/loss feed. Documented totals are\nstringified decimals."
    • removedOutput schema / $defs / IpoProfitLossSummary / properties / total_cost / description
      Removed value: -"Total cost across all IPO holdings (stringified decimal)."
    • removedOutput schema / $defs / IpoProfitLossSummary / properties / total_return / description
      Removed value: -"Total return across all IPO holdings (stringified decimal)."
    • removedOutput schema / $defs / IpoProfitLossSummary / properties / total_value / description
      Removed value: -"Total current value across all IPO holdings (stringified decimal)."
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / description
      Removed value: -"Returned by `ipo_profit_loss`. Summary and per-stock breakdown combined\nunder a `{summary, items}` wrapper object built by the tool."
    • removedOutput schema / properties / items / description
      Removed value: -"Per-stock breakdown items."
    • removedOutput schema / properties / summary / description
      Removed value: -"Aggregate cost/value/return totals."
    • removedOutput schema / title
      Removed value: -"IpoProfitLossResponse"
  3. Changed1 schema field changedv0.5.6
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$defs": {
      +    "IpoProfitLossItem": {
      +      "description": "A single per-stock IPO profit/loss breakdown item. Subset of upstream\nfields; monetary and rate fields are stringified by the transform pipeline.",
      +      "properties": {
      +        "cost": {
      +          "description": "Cost basis for this stock (stringified decimal).",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "current_value": {
      +          "description": "Current market value for this stock (stringified decimal).",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "return_rate": {
      +          "description": "Return rate for this stock (stringified decimal / percentage).",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "symbol": {
      +          "description": "Security symbol, e.g. \"6871.HK\".",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "IpoProfitLossItems": {
      +      "description": "The items side of the IPO profit/loss feed. The documented portion is\n`items[]`.",
      +      "properties": {
      +        "items": {
      +          "description": "Per-stock profit/loss breakdown entries.",
      +          "items": {
      +            "$ref": "#/$defs/IpoProfitLossItem"
      +          },
      +          "type": [
      +            "array",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "IpoProfitLossSummary": {
      +      "description": "The summary side of the IPO profit/loss feed. Documented totals are\nstringified decimals.",
      +      "properties": {
      +        "total_cost": {
      +          "description": "Total cost across all IPO holdings (stringified decimal).",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "total_return": {
      +          "description": "Total return across all IPO holdings (stringified decimal).",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "total_value": {
      +          "description": "Total current value across all IPO holdings (stringified decimal).",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "description": "Returned by `ipo_profit_loss`. Summary and per-stock breakdown combined\nunder a `{summary, items}` wrapper object built by the tool.",
      +  "properties": {
      +    "items": {
      +      "$ref": "#/$defs/IpoProfitLossItems",
      +      "description": "Per-stock breakdown items."
      +    },
      +    "summary": {
      +      "$ref": "#/$defs/IpoProfitLossSummary",
      +      "description": "Aggregate cost/value/return totals."
      +    }
      +  },
      +  "required": [
      +    "summary",
      +    "items"
      +  ],
      +  "title": "IpoProfitLossResponse",
      +  "type": "object"
      +}
  4. Addedv0.4.5
  5. Removedv0.4.0
  6. Addedv0.3.2
  7. Removedv0.3.1
  8. Addedv0.2.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already indicate it's read-only and idempotent. The description adds that it shows a summary and per-stock breakdown, but does not elaborate on pagination behavior or data freshness, which would be helpful.

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 extremely concise: a single sentence plus a note on period. No unnecessary words.

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?

With output schema present and annotations, the description is fairly complete. However, it could mention that results are paginated via page and size parameters, which are only in schema.

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% and the description adds no additional meaning beyond the schema. It reiterates the period values but no new information.

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 it shows IPO profit/loss summary and per-stock breakdown, with the period parameter. This distinguishes it from sibling tools like ipo_calendar or ipo_detail which have different focuses.

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 description mentions the period parameter options but does not provide guidance on when to use this tool versus alternatives, nor does it specify when not to use it.

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