Skip to main content
Glama
longbridge

longbridge

Official

IPO Profit / Loss

ipo_profit_loss
Read-onlyIdempotent

View IPO profit and loss summary with per-stock breakdown for your account. Filter by period: all, year-to-date, 1 year, or 3 years.

Instructions

Show IPO profit/loss summary and per-stock breakdown for the current account. period: all (default), ytd, 1y, 3y.

Input Schema

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

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

Annotations already indicate readOnlyHint, idempotentHint, and openWorldHint, covering safety and idempotency. The description adds no further behavioral traits beyond what annotations provide, so score is neutral at 3.

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—two sentences with no redundant words. It front-loads the core purpose and immediately lists parameter details, making it efficient for an agent.

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?

Given no output schema, the description omits return value details and pagination behavior. However, for a simple summary tool, the information is adequate though incomplete for full context. Scores 3.

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 description coverage is 100%, with each parameter well-documented. The description reiterates period values but adds no new meaning beyond the schema, so baseline 3 applies.

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 shows IPO profit/loss summary and per-stock breakdown, specifying the resource (IPO profit/loss) and action (show). It distinguishes from sibling IPO tools by focusing on profit/loss rather than calendar or detail.

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 indicates it's for the current account and lists period options, providing clear context. However, no guidance on when to use this tool versus related siblings like ipo_detail or ipo_calendar, nor any exclusions.

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