Bybit MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

getDeliveryRecord

Read-only

Retrieve delivery records for Bybit futures and options contracts. Filter by category, symbol, and time range to get historical delivery data within 30-day windows.

Instructions

Query delivery records of USDC futures, Inverse futures, and Options.

Unified account covers: USDT futures / USDC contract / Inverse futures / Options
Classic account covers: Inverse futures

Time range rules:

Without both startTime and endTime: returns last 30 days by default
Only startTime provided: returns from startTime to startTime + 30 days
Only endTime provided: returns from endTime - 30 days to endTime
Both provided: endTime - startTime must be ≤ 30 days

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>"
    },
    "name": "getDeliveryRecord"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`symbol`	No
`endTime`	No
`expDate`	No
`category`	Yes
`startTime`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.11Jun 19, 2026

TDQS

A3.5/5.0

Behavior4/5

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

With readOnlyHint=true already present, the description adds meaningful behavioral context: the default 30-day window, how startTime and endTime interact, and the unified/classic account coverage differences. This goes beyond the annotations and helps the agent understand the tool's default data-scoping behavior.

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 tightly organized with a one-line purpose, concise account-coverage bullets, and a clearly formatted list of time-range rules. Every sentence contributes information, and the most important constraints are front-loaded.

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?

There is no output schema and the description does not describe the shape or fields of a delivery record. It also omits any explanation of pagination-related parameters or how symbol and expDate affect results, leaving a significant gap for an agent trying to interpret the response.

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

Parameters2/5

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

The schema has 0% description coverage, so the description must compensate. It does explain startTime and endTime in detail, but it leaves cursor, limit, symbol, expDate, and category (beyond the enum values) semantically undocumented. This is only partial compensation for a seven-parameter tool.

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 opens with a specific verb and resource: 'Query delivery records of USDC futures, Inverse futures, and Options.' It also clarifies account coverage, making the tool's scope unmistakable and distinct from price-related siblings like getDeliveryPrice and getNewDeliveryPrice.

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 detailed time-range rules and account coverage, but it never explicitly says when to use this tool versus the related delivery-price or record tools. There is no mention of alternatives or exclusions, leaving the agent to infer selection from the tool name alone.

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

Deploy Server