Skip to main content
Glama
bybit-exchange

Bybit MCP Server

Official

getServerTime

Retrieve Bybit server time in seconds and nanoseconds to synchronize your local clock and prevent timestamp errors when placing authenticated orders.

Instructions

Query Bybit server time, returned in both seconds and nanoseconds precision.

Use this endpoint when you need to:

  • Synchronize your local clock with Bybit server time before constructing authenticated requests

  • Verify timestamp alignment to avoid request timestamp errors (error code 10002)

Returns timeSecond (Unix timestamp in seconds) and timeNano (nanosecond precision).

Do not use this endpoint for market data — use getTickers or getMarketKline instead.

Notes:

  • During periods of extreme market volatility, this endpoint may experience increased latency

  • No authentication required

Agent hint: Use this endpoint to obtain the current Bybit server time for clock synchronization. Call this before placing orders if you suspect your local clock is out of sync with the server. This is a utility endpoint — do not use it for market data; use getTickers or getMarketKline instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, but description covers return values (timeSecond, timeNano), notes on latency during volatility, and states no authentication required. Does not mention rate limits, but for a simple read-only endpoint this is sufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is clear and front-loaded with purpose, but slightly verbose with repeated agent hint. Still well-structured and easy to parse.

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

Completeness5/5

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

Given no parameters and no output schema, description fully covers what the tool does, its return values, usage notes, and caveats. Complete for a utility endpoint.

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?

No parameters; schema coverage is 100% trivially. Baseline is 4 per instructions. Description adds no param info but is not needed.

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 queries Bybit server time and returns seconds and nanoseconds. It distinguishes from siblings by explicitly stating 'Do not use this endpoint for market data' and directing to getTickers or getMarketKline.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly describes when to use (clock synchronization, avoid timestamp errors) and when not to use (market data), with alternative tool names. Provides concrete use cases and error codes.

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/bybit-exchange/trading-mcp'

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