Skip to main content
Glama
Sign In
bybit-mcp

bybit-mcp

by JohnnyWic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_pre_upgrade_closed_pnl

Retrieve closed profit and loss records from before a system upgrade for a specified trading pair and product category.

Instructions

Get pre-upgrade closed PnL records.

Args: category: Product type: linear, inverse. symbol: The trading pair, e.g., BTCUSDT. limit: Number of records (default: 50, max: 100).

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": {
      "category": "<category>",
      "symbol": "<symbol>"
    },
    "name": "get_pre_upgrade_closed_pnl"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYes
symbolYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits beyond the basic action. There is no mention of read-only status, side effects, or permission requirements, which are important for an agent to know before invoking.

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 one-line purpose followed by a brief parameter list. Every sentence adds value and is front-loaded with the main function. No redundant or extraneous information.

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?

While the parameter semantics are clear, the description lacks information about the return value format, pagination behavior, or any prerequisites. For a simple query tool with no output schema, this is minimally acceptable but could be improved.

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?

The description adds meaningful context beyond the schema: it explains 'category' as 'Product type: linear, inverse', 'symbol' with an example, and 'limit' with default and maximum values. This compensates for the 0% schema description coverage.

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 'Gets pre-upgrade closed PnL records,' specifying the resource (closed PnL) and distinguishing it from siblings like 'get_closed_pnl' with the 'pre-upgrade' qualifier. The argument list further clarifies the scope.

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 such as 'get_closed_pnl' or 'get_closed_options_positions'. There is no mention of preconditions or scenarios where this tool is appropriate.

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

Deploy Server

Other Tools