Skip to main content
Glama
Sign In
Bybit MCP Server

Bybit MCP Server

Official
by bybit-exchange
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

queryDepositRecords

Read-only

Retrieve Bybit on-chain deposit records filtered by coin, transaction ID, or record ID within any 30-day period. Works with both main and sub UID API keys.

Instructions

Query on-chain deposit records

  • Supports both main and sub UID API keys

  • Time range (endTime - startTime) must be under 30 days; defaults to last 30 days

  • startTime / endTime are millisecond timestamps but effective at second-level granularity

  • When id is provided, it takes highest priority over other filter params

  • txID only works for data from Jan 1, 2024 onward

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "queryDepositRecords"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
coinNo
txIDNo
limitNo
cursorNo
endTimeNo
startTimeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.11

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, so the safe read nature is known. The description adds meaningful behavioral detail beyond that: main/sub API key support, the 30-day window constraint, millisecond-to-second granularity quirk, id precedence, and the txID date cutoff. This is strong supplementary transparency, though it omits any pagination or response 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 a tight set of four bullet points with no fluff. The core purpose is front-loaded, and every bullet adds a distinct non-obvious fact. It is easy to scan and parse.

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?

The description covers the most important behavioral constraints for this 7-parameter read-only tool. However, with no output schema and no explanation of cursor-based pagination, coin filtering, or limit semantics, it is not fully complete for an agent that may need to paginate or filter by coin.

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 0%, so the description carries the burden for parameter meaning. It usefully explains startTime/endTime range and granularity, id precedence, and txID date restriction. However, it says nothing about coin, limit, or cursor, leaving cursor especially opaque for an agent needing pagination.

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 on-chain deposit records'. This clearly distinguishes it from sibling tools like queryInternalDepositRecords and querySubMemberDepositRecords by emphasizing 'on-chain' deposits. No ambiguity about what the tool does.

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 provides useful usage constraints such as the 30-day time range, id priority, and txID date limitation. However, it does not explicitly state when to use this tool versus the closely related sibling tools like queryInternalDepositRecords or querySubMemberDepositRecords. The usage guidance is implied rather than explicit.

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