Skip to main content
Glama
longbridge

longbridge

Official

IPO Profit / Loss

ipo_profit_loss
Read-onlyIdempotent

Retrieve IPO profit/loss summary with total cost, value, return, and per-stock breakdown including symbol, cost, current value, and return rate. Filterable by period: all, YTD, 1Y, 3Y.

Instructions

Show IPO profit/loss summary and per-stock breakdown. Returns {total_cost, total_value, total_return, items[]{symbol, cost, current_value, return_rate}}. period: all/ytd/1y/3y.

Input Schema

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

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryYesAggregate cost/value/return totals.
itemsYesPer-stock breakdown items.
Behavior3/5

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

Annotations declare readOnly, idempotent, openWorld. Description adds return structure but no extra behavioral details beyond annotations. 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?

Two sentences, front-loaded with purpose and return structure, no wasted 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?

Given output schema exists, description adequately covers purpose, return structure, and period filter. Could mention prerequisite (e.g., IPO holdings) but not required.

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 100%; description only adds period values ('all/ytd/1y/3y') beyond schema. Minimal added value.

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?

Clearly states verb 'Show' and resource 'IPO profit/loss summary and per-stock breakdown', with explicit return fields. Differentiates from siblings like ipo_calendar, ipo_detail, etc.

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?

Describes period filter but no explicit when-to-use or alternatives. Implied use for IPO performance tracking among IPO-related tools.

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