Skip to main content
Glama
ethancod1ng

Bybit MCP Server

by ethancod1ng

get_orderbook

Retrieve real-time order book depth data for a specified trading symbol on Bybit, providing bid and ask price levels with quantities to analyze market liquidity and price discovery.

Instructions

Get the order book depth for a trading symbol

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes
limitNo

Implementation Reference

  • Core handler function that executes the logic for fetching the order book from Bybit API using RestClientV5.
    async getOrderBook(symbol: string, limit: number = 25) {
      try {
        const response = await this.client.getOrderbook({
          category: 'spot',
          symbol: symbol,
          limit: limit
        });
        return response;
      } catch (error) {
        throw new Error(`Failed to get order book for ${symbol}: ${error instanceof Error ? error.message : JSON.stringify(error)}`);
      }
    }
  • MCP server dispatch handler for 'get_orderbook' tool call, delegating to BybitClient.getOrderBook.
    case 'get_orderbook':
      result = await this.client.getOrderBook(
        args.symbol as string,
        args.limit as number
      );
      break;
  • src/tools.ts:24-32 (registration)
    Registration of the 'get_orderbook' tool in the MCP tools array, including name, description, and input schema.
    {
      name: 'get_orderbook',
      description: 'Get the order book depth for a trading symbol',
      inputSchema: {
        type: 'object',
        properties: OrderBookSchema.shape,
        required: ['symbol']
      }
    },
  • Zod schema definition for input validation of the get_orderbook tool (symbol and optional limit).
    export const OrderBookSchema = z.object({
      symbol: z.string().describe('Trading symbol (e.g., BTCUSDT)'),
      limit: z.number().min(1).max(500).optional().describe('Number of entries to return (default: 25)')
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does but lacks details on traits like rate limits, authentication requirements, or what 'order book depth' entails (e.g., bid/ask levels). This leaves gaps for an AI agent to understand operational constraints.

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 single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 the complexity of a trading tool with 2 parameters, no annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects, parameter details, or return values, leaving significant gaps for an AI agent to effectively use the tool.

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 must compensate, but it only mentions 'trading symbol' without adding meaning beyond the schema's 'symbol' parameter. It doesn't explain the 'limit' parameter or provide context like default behavior or typical values, resulting in minimal added value.

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 the action ('Get') and resource ('order book depth for a trading symbol'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_price' or 'get_24hr_ticker', which might also relate to trading data, so it lacks sibling distinction for a perfect score.

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. For example, it doesn't mention that this is for depth data rather than price or ticker information, nor does it reference sibling tools like 'get_price' for different market data needs.

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/ethancod1ng/bybit-mcp-server'

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