Skip to main content
Glama
workspace

bybit-mcp-server

by workspace

get_closed_pnl

Read-only

Retrieve closed profit and loss records for linear or inverse products, filtered by symbol, time range, and pagination.

Instructions

Query closed profit and loss records.

    Args:
        category: Product type - linear, inverse
        symbol: Symbol name
        startTime: Start timestamp in milliseconds
        endTime: End timestamp in milliseconds
        limit: Limit per page (max 100, default 50)
        cursor: Pagination cursor
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
cursorNo
symbolNo
endTimeNo
categoryYes
startTimeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description adds some value beyond annotations (readOnlyHint, openWorldHint) by noting limit max 100 and default 50. However, it does not mention pagination behavior, response structure, data freshness, or any side effects. Given annotations already cover read-only and open-world, a score of 3 is appropriate.

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: one line for purpose and a compact parameter list. Every sentence adds value, and there is no extraneous text. It follows a clear, front-loaded structure.

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 6 parameters, an output schema, and siblings like get_trade_history, the description is adequate but not complete. It lacks context on what 'closed P&L' means practically, typical use cases, or authentication needs. The presence of an output schema reduces the need to describe return values, but usage context is insufficient.

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

Parameters4/5

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

Schema coverage is 0%, so the description fully compensates by explaining all 6 parameters: category as product type, symbol as name, start/endTime as timestamps in ms, limit with max/default, and cursor for pagination. Some details like exact constraints on symbol format are missing, but overall it adds significant meaning.

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 begins with 'Query closed profit and loss records,' which is a specific verb+resource pair. It clearly distinguishes this tool from siblings like get_order_history or get_trade_history by focusing on closed P&L data.

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 provides no guidance on when to use this tool versus alternatives. It lacks context such as prerequisites, when to use pagination, or how it relates to other account history tools. The sibling list is unhelpful without explicit comparison.

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/workspace/bybit-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server