Skip to main content
Glama
Sign In
Bybit MCP Server

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

getPendingOrders

Read-only

Retrieve pending P2P orders from Bybit. Filter by side, status, token, and time range to access orders from the last 90 days, up to 180 days.

Instructions

Get a list of pending P2P orders. Returns 90 days of orders by default. Orders are accessible up to 180 days in the past.

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": {
      "page": "<page>",
      "size": "<size>"
    },
    "name": "getPendingOrders"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYes
sideNo
sizeYes
statusNo
endTimeNo
tokenIdNo
beginTimeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.11

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare read-only behavior, and the description adds useful retention-window context. However, it does not disclose pagination behavior, default sorting, or what counts as 'pending', leaving some behavioral details open.

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 only two sentences, with the core purpose front-loaded and no wasted words. The retention context earns its place alongside the primary statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given seven parameters, no output schema, and no parameter descriptions, the description is too thin for an agent to call the tool with confidence. It lacks details on pagination, timestamp formats, status/side semantics, and how to request data beyond the 90-day default.

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

Parameters1/5

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

Schema description coverage is 0% and the description adds no parameter-level meaning. The names page, size, side, status, beginTime, endTime, and tokenId are self-evident to some degree, but there is no guidance on formats, allowed values, or how the 90-day default relates to beginTime/endTime.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific action, resource, and scope: 'Get a list of pending P2P orders.' This is enough to distinguish it from many generic order-list siblings, though it does not explicitly name a sibling alternative.

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 implies use when pending P2P order data is needed and provides temporal context ('90 days by default', 'up to 180 days in the past'), but it gives no explicit guidance about when not to use this tool or which sibling tools should handle other order scenarios.

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